Hi everyone, I''ve noticed an inconsistency in the way rails deals with uncountable resources and restful routes. Basically if you map an uncountable resource rails will append ''_index'' to the end of some routes to avoid route clashes between the routes that deal with singular resources and plural resources. That''s all fine but on the other end, with the polymorphic path generator, it doesn''t generate the correct path. using form_for [@podcast_series] generates something like podcast_series_path. If called from a form it should be smart enough to realise that we want the update path and call podcast_series_index_path. Has anyone else come up against it? I''m not savvy enough to write a patch for rails so how do I get this investigated? Does anyone have a solution? Cheers, Brendon --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
Brendon Muir wrote:> Hi everyone, I''ve noticed an inconsistency in the way rails deals with > uncountable resources and restful routes. > > Basically if you map an uncountable resource rails will append > ''_index'' to the end of some routes to avoid route clashes between the > routes that deal with singular resources and plural resources. That''s > all fine but on the other end, with the polymorphic path generator, it > doesn''t generate the correct path. using form_for [@podcast_series] > generates something like podcast_series_path. If called from a form it > should be smart enough to realise that we want the update path and > call podcast_series_index_path. > > Has anyone else come up against it? I''m not savvy enough to write a > patch for rails so how do I get this investigated? Does anyone have a > solution? > > Cheers, > > BrendonI noticed that this bug is still resides in Rails. Is there a path for this problem? How did you fix it? -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.