Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

Ruby Rails Routes and Resources A Route to an Index Action Populating the View

Oğulcan Girginc
Oğulcan Girginc
24,848 Points
Posted by Oğulcan Girginc
Oğulcan Girginc
24,848 Points

@pages.each vs. Page.all.each for the view

Is it a better practice to use

<% @pages.each do |page| %>
  <p>
    <%= page.title %>
  </p>
<% end %>

as Jay used or using

<% Pages.all.each do |page| %>
  <p>
    <%= page.title %>
  </p>
<% end %>

is considered better practice?

1 Answer

Marco van Vemden
Marco van Vemden
12,553 Points
Marco van Vemden
Marco van Vemden
12,553 Points

Hi Oğulcan,

The first example is the better practice; in the view you are using the instance variable (@pages) that was set in the controller. The controller can be thought of as a middleman between models and views. It makes the model data available to the view so it can display that data to the user, and it saves or updates user data to the model.

In the second example you are loading the (Pages) model data in the view, and display it.