PLEASE COMMENT YOUR CODE. Do not clone this repository. Instead, download the zip, extract the contents,
git init
,git add .
,git commit -m "initial commit - base project"
and add your remote. Please do this before you leave for the day.
For this weekend challenge you'll be building a movie application! We'll be able to see movies that exist in our DB. We'll also be able to see detailed view for each individual movie, including genres associated with that movie. We'll also be able to edit our movie's information.
- Create a database named
saga_movies_weekend
- Run the queries from
database.sql
on thesaga_movies_weekend
database. - You will need to create the junction table between the
movies
andgenres
tables!
npm install
npm run server
npm run client
We've given you some starter genres in the database. Feel free to change or add some with Postico.
We've added some movie posters in the public/images
folder, and the database is set up to use them.
Genres can be applied to many different movies. Movies can have multiple genres. This is Many-to-Many! Junction Table time!
NOTE: Start by taking inventory of the existing code. Part of the work for setting up sagas has been done for you.
This should display all of the movies in the movie database. When a movie poster is clicked, a user should be brought to the /details
view.
This should show all details including genres, for the selected movie.
The details page should have the buttons:
Back to List
button, which should bring the user to the Home PageEdit
button, which should bring the user to the Edit Page
Base functionality does not require the movie details to load correctly after refresh of the browser.
This should show:
- an input field (for changing the movie title), for the selected movie.
- a textarea (for changing the movie description)
The details page should have the buttons:
Cancel
button, which should bring the user to the Details PageSave
button, which should update the title and description in the database and bring the user to the Details Page
Base functionality does not require the current values (the existing movie title and description) to populate in the input and textarea.
Base functionality does not require the movie information to load correctly after refresh of the browser.
As one of your last projects, it's possible you will be sharing this with employers, so be sure to follow best practices and make it look good!
- Invest some time in styling it up!
- Research grids for you movie posters on the Move List page
- Add route change animations
- Commit your code frequently! You should have at 15+ commits on a project of this size. Use branches to help break down your features.
- Comment your code.
- Update this README to include a description of the project in your own words.
- Display the current values in the input (title) and textarea (description) on the Edit Page
- Display all genres on movie list page. Research array_agg to make this possible.
- Move sagas and reducers out of your
index.js
and into separate files (ideally insrc/redux/reducers
andsrc/redux/sagas
folders). - Allow the user to refresh the details or edit page. The url for the details page would be something like
/details/1
for movie with id of1
. Research react router params. - Allow the user to add a genre to a movie.
- Allow the user to remove a genre from a movie.
- Only display the top 10 movies, and allow the user to search for movie titles with a search bar on the home page (you can do this on the client side or the server side, server side is a bigger stretch, but good practice).
- Create an
Admin
page. Add a link from theHome
page to theAdmin
page. The page should initially display a login form (an input for username and an input for password). When the user enters the correct username (camera
) and password (action
), the page should display a form to add genres to the database, and a list of all of the genres with anx
to remove them from the database. Note: This isn't actually secure, but it's pretty fun, and really good practice.