Mark Weston wrote: > On 7 October 2010 09:35, Maksim Gudovsikov <[email protected]> wrote: >> >> That should help. >> >> Regards, Max. >> >> >> > Mmm, perhaps you meant that all models *should* be singular in rails. > Mine > weren't! However after a couple of quick search-and-replaces I had a > singular Task model and suddenly the form_for error went away. > Interesting > side-effect. Maybe warnings about pluralised models in the docs need to > be > in really BIG RED LETTERS so that idiots like me will notice them.
Remember: try to name your classes after what they actually represent! A Task object represents one Task, so you really *shouldn't* call it Tasks. > > Anyway, thanks for the reply. > > Mark Best, -- Marnen Laibow-Koser http://www.marnen.org [email protected] -- 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 [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-talk?hl=en.
