Topic: Best way to deal with nil objects in views...
"NoMethodError in Articles#suggested...
You have a nil object when you didn't expect it!"
Isn't too pretty. I can certainly check before iterating through a set of objects in the view itself, but it seems to me the template shouldn't have to deal with this sort of situation.
It would be nice to have the template fail gracefully when @articles is nil.
<% for article in @articles %>
Is there a better way to protect the views from these sorts of errors?