On Tue, Sep 23, 2008 at 5:32 PM, Andrew Kaspick <[EMAIL PROTECTED]> wrote: > >> However in your case, the route points to some nonsense controller >> that doesn't even exist. We could change *that* behaviour without >> breaking anything. >> > > That was my other thought actually as well; check the controller > "name" to see if it actually exists.
To me this seems like a pretty good compromise. I doubt anyone's expecting url_for to point to non-existent controllers, and if they are, it's hardly unreasonable for this to be fixed. This will involve a trip into the bowels of the routes implementation, but hopefully you come up better for the experience :) -- Cheers Koz --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
