Welcome to the Treehouse Community
The Treehouse Community is a meeting place for developers, designers, and programmers of all backgrounds and skill levels to get support. Collaborate here on code errors or bugs that you need feedback on, or asking for an extra set of eyes on your latest project. Join thousands of Treehouse students and alumni in the community today. (Note: Only Treehouse students can comment or ask questions, but non-students are welcome to browse our conversations.)
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and a supportive community. Start your free trial today.
Oğulcan Girginc24,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?
Marco van Vemden12,553 Points
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.