/rails-programmer-profile-partials-v-000

Primary LanguageRubyOtherNOASSERTION

#Objectives

  1. Practice using partials.
  2. Use all the different techniques you've learned in this unit.
  3. DRY up your views with locals

Overview

We have a Rails app that showcases some of our favorite programmers. The landing page is an index of all the programmers, and users can click on each programmer to see his or her profile page. There's just one problem - the views are loaded with repetition and clunky iteration, and could use some serious refactoring. Your job is to clean up programmers/index.html.erb and programmers/show.html.erb by using partials.

Instructions

Fork and clone the lab. Run bundle install and rake db:migrate, then rake db:migrate RAILS_ENV=test. Next, seed the database with some programmers - run rake db:seed - and start the sever to see the app in the browser.

Run rspec and make the tests pass one at a time! The app will continue to have the same functionality (keep checking it in the browser), but you'll be making the following partials to clean up the views:

  1. A partial to render the navbar.
  2. A partial to render all the programmers on the index page (see the example above!).
  3. A bonus partial to abstract away some of the repetition in app/views/programmers/show.html.erb. More details on that in the next section.

Bonus

This part is a little more complex than the previous two steps, and will require you to get a little more creative.

When you look at app/views/programmers/show.html.erb, you will probably notice a pattern in how several of the attributes are rendered (specifically home_country, quote, and claim_to_fame. They each seem to be in a <p> tag with a bold capitalized label followed by the value for the given attribute. You'll want to render each of these with a single partial, app/views/programmers/_attribute.html.erb. Here are two hints to set you on the right track:

You'll have to pass local variables to the partial — check the resources below for more tips.

Resources