On 13 Jul 2011, at 08:20, Corin Langosch wrote: > What about making the polymorphic routing in rails to try a plural route > first. If it fails, try a singleton route. If it fails, raise. > > This is not the nicest and most performant way (the result could be cached in > production so it doesn't really matter in the end) but I guess it should > solve most cases. Or is this too much magic?
That's certainly one of the solutions I've thought about and I've got a GitHub issue (#1769) assigned to me regarding this issue so it's on my todo list once 3.1 has shipped. Andrew -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
