>
>
> To sum up mu thoughts, I'm 200% for a localization API/hook so we
> wouldn't have to monkey patch the core every time you guys change
> something. But honestly, having a diversity of localization solutions
> is awesome and I would hate to see this new API/hook forcing people to
> do things a
On Jul 14, 2007, at 11:13 AM, Bernardo de Pádua wrote:
> I also think this kind of nesting is the logical
> thing to support, as I've seen many users think (myself included) that
> it was already there in Rails, try it and be surprised with the errors
> it caused. If the Rails way was wanting t
+1
Rails has usually been about clean queries over performant
ones. :include came way after associations, for example, but :include
solved a real problem visible in real applications.
No benchmarking makes sense outside the context of a real
application, and this patch would benefit real a
On Jul 7, 2007, at 8:14 AM, Evan Weaver wrote:
>
> I tend to agree with this. I don't really understand the need to
> "canonically" identify a resource based on its context.
>
> Other thoughts?
>
> Evan
The simple reason would be that you want your URLs to look that way.
Joshua
--~--~
iated with il8n and look at
a specific proposal for how to solve this. Many other
frameworks provide simple solutions to this without adding complexity
beyond variable interpolation.
Joshua Sierles
--~--~-~--~~~---~--~~
You received this message because you are subsc
r_filter to application.rb to set the Content-Type
header correctly
Rails now defaults to utf-8 Content-Type.
Joshua Sierles
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
T
