Backend Routes

[bamorgan13]

• [x] Start out with just a movies controller instead of tv shows and videos. If you add in tv shows later on you can add in this functionality and layering, but at the beginning stages of your project just focus on the movies (you can leave the controllers in this document, just wanted to be clear where you should be starting during implementation).
• [x] Since you are only going to be interacting with your own (current_user's) list videos, you could remove the nested users and simplify your requests to "/api/list_videos", using the rails current_user helper method that you set up in your application controller
• [x] If you store genres on the movies (and potentially tv shows) table directly, they will not have an id for you to be able to make a request for ("/api/genres/:id"). You can instead either specifically send a request to "/api/movies" with a :genre parameter and return all movies that match that genre, or keep this genre controller that consolidates the same request between all movies and all tv shows.
• [x] Similarly, your search feature will require a backend route that accepts search terms as parameters. You could send these requests directly to "/api/movies" and then just respond with movies that match the search if that parameter is present, or you could implement a specific search controller that will consolidate those results between movies and tv shows.