In this project, we'll practice populating pages with data from a database.
We'll also build some forms to add records to tables.
There's an image of the ERD of the database you have to work with in the root-level folder of the application, erd.png.
You can also check out the comments at the top of each of your models in app/models to remind yourself of what columns it has.
Here's your target. Not all parts are required for now; in particular, the edit forms are optional challenges. You've got the all tools needed, but they have quite a few moving parts; we can finish them together.
The required tasks are:
/usersshould- display all the users
- a link to get to details for each user
- a form to add a new user
/users/[USERNAME]should- display the username of the user
- the photos posted by the user
/photosshould have a form to add a new photo/photos/[ID]should- display the details of a photo
- displays the comments that have been made on the photo
- have a form to add a comment to the photo
- As often as you like, reset your database with dummy data:
rails dummy_data - Start the web server:
bin/server - Always Be Committing at
/git - Check out your database visually at
/rails/db - Run
rails gradeas often as you like to see how you are doing, but test your app manually first to make sure it matches the target's behavior.
-
I added some validations, rules to try and help prevent bogus data from entering your tables, to your models. We'll discuss these next week.
-
Don't be alarmed by the number of automated tests. Most of them are there as hints to help you structure your forms correctly.
-
It's okay to View Source on the target to get hints on what HTML we used.
-
When you make forms, don't forget to add a
<label>for every form control (<input>,<textarea>, etc). The<label>should have afor=""attribute that matches theid=""attribute of the input. For example,<label for="zebra">Fan</label> <input id="zebra" type="text" name="qs_fan_id">