Joe Smith wrote: > The second is good in that there is never more information than is > needed to > identify resources. It is good if you want to let a tenant be moved to a > new > building in the tenant edit form. It is bad in that the forms for > creating a > resource require specifying the parent. (Imagine if when creating a > comment > for a blog post, the form required you to specify which story you were > commenting on. Yuck!)
Upon further thought: It *would* a pain if you had to specify the blog entry in order to post a comment. But the BlogComment model knows which BlogEntry it's part of. Thus the BlogCommentController can make @blog_entry available to the form so you don't have to. Am I missing something? -- 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.
