cortadev / dizney-plus Goto Github PK

• /home ought to be just /
• /search doesn't need a GET - the search form appears as a dynamic element, rather than a full page.
• /search queries should use a POST method rather than PATCH.
• You should add a route POST /watchlist/add/:showId to add a new show to the current Profile's watchlist.
• GET /watchlist/:id the id here can be left out GET /watchlist and always use the current Profile's watchlist.
• DELETE /watchlist/:showId instead of DESTROY /movies/:id This way, you use one endpoint for both movies' and for series'.
• Add user interaction routes for signup, login, etc.
• /select-avatar ought to be a PATCH /users/profiles/ with the form being on GET /users/profiles/edit
• Make profile routes RESTful: For example: GET /add-profile should be: GET /users/profiles/new GET /select-profile should be: GET /users/profiles.
• Remove GET /edit-profiles route, there should be links on the GET /users/profiles page to DELETE a specific profile.
• What is Brands and is that related to Collections? What routes are needed for collections?

Hello Disney+ Team!

After reviewing your feature list documentation, here is a list of our feedback. Please address these concerns today (Thursday July 9) and send a message in your slack channel when addressed.

• In general these features leave too much to interpretation - add a lot of details about what actions a user can take, and what authorizations are needed to do so. Instead of "User Auth" specify each of the features needed: "User login, signup, profile page, etc."
• How will the catalogue be searchable? By Genre, Type, Family Friendly, Popular, etc.
• Make watch list required and support all four CRUD operations for creating new lists. Also support CRUD operations for adding to and modifying these watch lists.
• Likes/Ratings should support all four CRUD operations
• User Profile page should act as a view for watch lists and likes/ratings
• Add Heroku hosting of site and database as feature
• Add high quality README.md and documentation as feature
• Add one or two Bonus / Stretch goals that you will implement if you have time.

Because your feature list is somewhat sparse, you should call a TA to do final review as soon as practical.