> In digging into this a bit more, I had mistakenly been under the > impression that it was the controller that was used to infer this > path, but it actually turns out the be the model object. Does it > really make sense to let the naming of a model object bleed so far > through the application layer without a "no, use this name instead" > fallback?
There actually is a fallback at present: <%= form_for @person, :url=>some_other_path do ... You could probably also override the values returned by YourClass.model_name to achieve the same thing. ree-1.8.7-2010.01 > Person.model_name => "Person" ree-1.8.7-2010.01 > Person.model_name.plural => "people" Personally though I just wear the url ugliness and have /forum_threads rather than worrying too much about it. Sure it's not gorgeous but you stay on the golden path and you're finished thinking about it in a few minutes. -- 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.
