- Use the
collectionkeyword with partials - Pass a collection to the render method
- Handle empty collections
Up until now our only way to render collections was somewhat manually. We could iterate over an array and render the partial for each object in the array. Let's see how Rails can abstract this into a nicer syntax.
Make sure you run rake db:seed before you test out the app in your browser. Because this lesson focuses on using the collection keyword with partials, we've hard-coded in the connection between authors and posts. In the posts controller create action, we link the newly created post with the first author in the database.
Currently, our posts#index view is manually rendering the partial in a loop.
<% @posts.each do |post| %>
<%= render :partial => "post", {:locals => {:post => post}} %>
<% end %>Rails offers a great way to render a collection using a partial by passing the collection option to the render method.
<%= render :partial => "post", :collection => @posts %>Our code is tighter and both more abstract and more clear. Another even more abstract method Rails gives us to do this is passing an array directly to the render method.
<%= render @posts %>This approach is a bit more abstract. Under the hood Rails uses the convention that you will have a partial with the name of the models in the collection. Rails will even render a collection of heterogeneous models ([customer, order, customer]) calling the correct partial for each one.
What happens if the collection you pass to your render call is empty? If you
don't handle this exception the render method will return nil and nothing will
appear on the screen. A useful trick is to use the || operator to print
something to the screen to alert the user to this.
<%= render(@posts) || "There are no blog posts!" %>Note: When dealing with an empty collection, you'll need to use () to
wrap that collection.
As always, Rails has tried to abstract commonly used functionality into more terse and implicit code. Experiment with these tricks in the upcoming lab.