Would merge work? Something like (off the top of my head):
Shift.includes(:schedules).merge(Schedule.occuring_on(Date.today))
where .occuring_on is
def self.occuring_on(day)
where(:occurs_on => day)
end
-Corey
On Thu, Oct 4, 2012 at 3:44 PM, r1git wrote:
> Does anybody know how to fix this
are not going anywhere. I don't see
an explanation in there about why they are wonderful.
But, since conversation is shut down, I guess we can all sit back and
continue to help teams recover from using your "wonderful" features.
-Corey
>
> On Wednesday, August 22, 2012 7
ice. My main concern is adding another layer of
abstraction/indirection that invites a bloat of routes.
-corey
> On Tuesday, August 21, 2012 11:09:05 PM UTC-3, Corey Haines wrote:
>>
>> So, there's been some commenting on the Routing Concer
So, there's been some commenting on the Routing Concerns that has been
added to rails.
https://github.com/rails/rails/commit/0dd24728a088fcb4ae616bb5d62734aca5276b1b
This seems to be adding no more functionality or ease of use than simply
using methods, Ruby's standard form of reuse.
Here's are
