(First time post here, so apologies in advance for any breaches of etiquette) I''m writing a plugin for myself to change how resource routes are named to work round the issues with the semi-colon. I can''t switch to edge as I''m using a e-commerce engine that I''ve written and the engines plugin doesn''t support edge at the moment. Leaving the issue of whether I should be using the engines plugin at the door, I''d like to be consistent with what might happen in 1.2.4. I''ve read <http://dev.rubyonrails.org/ticket/8558> and looked at the attached patch to stable and I was wondering what the likely outcome was as there has been no activity on the ticket for 7 weeks. AFAICS the questions that need answering are: 1. Should the semi-colon be changed in 1.2.x? 2. Should nested resources routes be named as in edge with the old names being deprecated? 3. Should new resource route functionality such as namespaces, associations, requirements and conditions be included? 4. Should ActionController::RecordIdentifier be included? 5. Should ActionController::PolymorphicRoutes be included? 6. Should MethodNotAllowed and NotImplemented be included? I''d be more than willing to write up an acceptable patch to stable if required. Andrew White --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---