> > > It's dirty, horrible, bad form, breaks the separation of layers... > > I don't know what you mean by dirty, it saves several lines of code > and when looking at the view code it is easier to see what is > happening than to see a variable that has to be hunted for in a filter > somewhere to find out what it is. >
It saves 4 lines of code, but breaks one of the principles of MVC layered separation. I'd say the 4 lines is worth it for keeping the application clean. > > Don't call the model from the view! > > @person.name is a model call from the view > I clarified my thoughts on this in a later post (10 March 2010 15:28), might I recommend reading that. Cheers, Andy -- 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.
