search

ga-wdi-boston / rails-api-one-to-many

Other
0 stars 92 forks source link

Reformat Lesson? #7

Open payne-chris-r opened 8 years ago

payne-chris-r commented 8 years ago

We kinda did this lesson a little differently than it’s currently set up. It looks like you did demo-CA-lab, demo-CA-lab, demo-CA-lab, and we had been doing one big Demo, then one big CA, then one big lab. I’m sure there are merits to both, but I have to say doing the whole thing I think gave them a better “big picture” snapshot. I should probalby just put this in an issue in the repo, but I’m happy to reformat this lesson if the @channel agrees this is the best approach while it’s fresh in my mind. Otherwise, it’ll be an issue for the next iteration!

payne-chris-r commented 8 years ago

013 did it this way: Demo, CA, lab: create routes and controller Demo, CA, lab: create Model Demo, CA, lab: set up relationship (has_many/belongs_to) 014 did it this way: Demo, CA, lab: Full crud, one action at a time, then relationships

payne-chris-r commented 8 years ago

Ok. I actually think doing it all the way through and then switching to CA, then Lab IS the right answer. We had tonnnnns of issues today with people doing generations and migrations in the WRONG repo.

gaand commented 8 years ago

@payne-chris-r We should discuss. The point is to iterate so they see things and practice and more practice over and over. Perhaps there's a better setup than what we've got so switching repositories is less of a problem, but not doing it as iterations defeats the pedagogical purpose @jrhorn424 and I were trying to achieve.

jrhorn424 commented 7 years ago

This iteration, I did:

For -single-resource. Then there were minimal changes to update to use relationships. Those changes followed this structure, one "feature" or action at a time, down through all layers. This README still needs to be updated. Apologies for that.