> As things stand currently, resource routing will broken in existing > sites if/when they upgrade to Rails 2.0. I've added a patch to ticket > 8558[1] that should work with both existing and 2.0 style resource > routes, giving deprecation warnings when using route names that won't > work in 2.0. > > It passes all the tests and I've checked it against my own sites and > everything appears to check out but I'd appreciate some feedback if > it breaks anyone's existing sites (or some +1s if it doesn't!)
Taking a look at this, my questions are: 1) Why are there still some hard coded semicolons in the route creation methods? 2) Shouldn't the seperator default to ; for 1.2.x and / for 2.x? Apart from that, it's looking good. > Thanks, > ANdrew White > > [1] http://dev.rubyonrails.org/attachment/ticket/8558/ > deprecated_resource_routing.2.diff > > > > -- 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 -~----------~----~----~----~------~----~------~--~---
