Current Schema file included in this lab has the foreign key column that needs to be created by the student.
Line 25: t.integer "artist_id"

The database does not actually have this column however.
If a student checks this file and sees this line, they would think to skip the creation of the foreign key column and run into issues later on.

This seems to be asking us to set up a custom method that save no keystrokes and no perf over @song.artist.name

Given Rails' fanatical devotion to convention over configuration, why would we do this?

The line is an extra it ... do line right above the show page spec.

i could not render the view #show/1, any idea why?

with following error:
Showing /home/ICanDoAllThingThroughChrist/code/labs/displaying-associations-rails-lab-v-000/app/views/songs/show.html.erb where line #2 raised:

undefined method `name' for nil:NilClass

The feature specs would always fail as such...

 Failure/Error: Artist.destroy_all

 NameError:
   uninitialized constant Artist
 # ./spec/features/artists_spec.rb:3:in `block (2 levels) in <top (required)>'

I fixed the issue by adding "require 'rails_helper'" to the feature tests. Not sure if it's required or if it's an issue with my environment.

need to make new action for songs

def new @song = Song.new end

Hi. This doesn't affect the lab tests or anything, but there's a syntax problem at the top of the views/songs/edit.html.erb page.

Line 1 says <h1>Editing <%= @song.name %></h1>, but since songs have titles instead of names, that line of code should be <h1>Editing <%= @song.title %></h1>.

This is just an edge case, since the lab doesn't focus on the "new" or "edit" pages at all; I just wanted to let you guys know that it's there.

---Sdcrouse

There is an error in the specs in line 32 of spec/features/artists_spec.rb.
Instead of expecting 2 songs, the singular 2 song is expected.

 it "shows the song count for each artist" do
   visit artists_path
   expect(page).to have_content("2 song")
 end

This same exact issue as:

learn-co-curriculum/displaying-associations-rails#2

May be a problem with the deployer?

This block suggests that we copy the values to test them in our console. The separation between the attributes and the return value is unclear and obscured, and created confusion.

2.2.3 :018 > new_person = Person.new
=> #<Person id: nil, name: nil, created_at: nil, updated_at: nil>

2.2.3 :019 > new_person.addresses_attributes={"0"=>{"street_address_1"=>"33 West 26", "street_address_2"=>"Floor 2", "city"=>"NYC", "state"=>"NY", "zipcode"=>"10004", "address_type"=>"work1"}, "1"=>{"street_address_1"=>"11 Broadway", "street_address_2"=>"Suite 260", "city"=>"NYC", "state"=>"NY", "zipcode"=>"10004", "address_type"=>"work2"}}
=> {"0"=>{"street_address_1"=>"33 West 26", "street_address_2"=>"Floor 2", "city"=>"NYC", "state"=>"NY", "zipcode"=>"10004", "address_type"=>"work1"}, "1"=>{"street_address_1"=>"11 Broadway", "street_address_2"=>"Suite 260", "city"=>"NYC", "state"=>"NY", "zipcode"=>"10004", "address_type"=>"work2"}}

2.2.3 :020 > new_person.save
(0.2ms) begin transaction
SQL (0.8ms) INSERT INTO "people" ("created_at", "updated_at") VALUES (?, ?) [["created_at", "2016-01-14 11:57:00.393038"], ["updated_at", "2016-01-14 11:57:00.393038"]]
SQL (0.3ms) INSERT INTO "addresses" ("street_address_1", "street_address_2", "city", "state", "zipcode", "address_type", "person_id", "created_at", "updated_at") VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?) [["street_address_1", "33 West 26"], ["street_address_2", "Floor 2"], ["city", "NYC"], ["state", "NY"], ["zipcode", "10004"], ["address_type", "work1"], ["person_id", 3], ["created_at", "2016-01-14 11:57:00.403152"], ["updated_at", "2016-01-14 11:57:00.403152"]]
SQL (0.1ms) INSERT INTO "addresses" ("street_address_1", "street_address_2", "city", "state", "zipcode", "address_type", "person_id", "created_at", "updated_at") VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?) [["street_address_1", "11 Broadway"], ["street_address_2", "Suite 260"], ["city", "NYC"], ["state", "NY"], ["zipcode", "10004"], ["address_type", "work2"], ["person_id", 3], ["created_at", "2016-01-14 11:57:00.405973"], ["updated_at", "2016-01-14 11:57:00.405973"]]
(0.6ms) commit transaction
=> true