strangeloop/site — comment on commit 041e01e2c4819fcce6bfcd94404f1850f50e6b99
File: vendor/engines/conference_sessions/app/controllers/admin/conference_sessions_controller.rb line 28
By puredanger:

Yeah, I think that would be cool.

On Tue, Feb 28, 2012 at 6:14 PM, Mario Aquino

wrote:
> The attendee.rb one is a scope that does a db lookup. This one will either take a request param or default to current year. I thought about just having it use params[:year]. It's used in another call in the same class that passes it down to the ConferenceSession model in the from_year lookup. That call actually does the same thing WRT assuming current year if no value is supplied. So either passing a request param or nil wouldn't affect that lookup. However, another place where that call is used is in the view, which uses the year to render the message in an H2 on that admin side. The default value coming as current year (if no param value is supplied) will be what makes the query that displays conf sessions return an empty set after Jan 1 and would match the heading appearing in the view. We could change the behavior so that the query that feeds sessions for the admin list view always shows all sessions for the max conf year. With that, we would show all sessions fr
> om last year until the first one for the current year gets added. I'd be fine with that kind of change if you feel strongly enough about it to put it in. Alex may like it better. :)
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/strangeloop/site/commit/041e01e2c4819fcce6bfcd94404f1850f50e6b99#commitcomment-1023740