tpyle / cs546final Goto Github PK

When the user clicks to remove a saved recipe from their saved list, the website will send a request to the server, server will remove the saved recipe from their list, and return on accept. The website should refresh to show this removal

On leaving a comment or rating, a request needs to be sent to the backend to update the rating or add the comment

When the user clicks random recipe, they are presented with filters.
The user will click any filters, and then a post is sent to the server.
The server should redirect the page to recipe/ID_of_random_recipe

When a user goes to view their recipes,
the website will request all recipes for that user
The server will need to match the userid to the current session ID, and send back the associated recipes for that user
The website will then render those recipes

Cards need to show actual recipe details from abbreviated list of recipes

Not sure if already done, but users registering on both sign in modal and register modal

The website needs to request the top X trending websites to the server
The serve should reply with the top X trending websites (perhps by popularity)
The website should render these recipe cards on the homepage

When a user goes to view their favorited recipes,
the website will request all favorited recipes for that user
The server will need to match the userid to the current session ID, and send back the associated favorited recipes for that user
The website will then render those recipes

When the user clicks save to favorites,
a request should be sent to the server. The server should add the recipe to the users favorites, and respond with some sort of ok message.
On reciept of ok, the recipe page should change "save to favorites" to "saved to favorites"

Scroll to top of recipe view page when a recipe card is clicked

The server should update popularity using some (however dumb) method

When the user selects filters, a request needs to be sent to the server with the filter.
The server needs to respond with all recipes in a json, (in abbreviated form)
The website needs to refresh its recipes to show what it recieved

When a user clicks the login button, it should disable until the request is resolved.

When editing a recipe, the website will send a post/put request to server, server will update recipe. No refresh needed on user end.

photos of recipes?

When deleting a recipe from existence, the website needs to send delete request, server needs to delete recipe, and reply to user. User page should re-render to show removal.

Currently clicking delete shows edit page (bug)

When the user types in the search bar, the website should re-route itself to the browse page.
A request then needs to be sent to the server.
The server needs to strip out any bad characters, and respond with a json of all applicable recipes (in abbreviated form)
The website should then display all recieved recipes to the user.

On editing the user info in userprofile, the website will send a post/put request to the server with the new data. On failure, it will alert the user. Such failure might be email already in use (if we want to have that check)

When user is prompted to input password to save, comment, or rate, it pops with the signin button. It should display a message saying "you must be logged in" or somethings when the sigin pops up for this reason.

-Includes buttons for logging in/logging out
-restricted access to userprofile,
-restricted access to add_to_favorites, comment, and rate

When the user filters their saved/favorited recipes, the website needs to send filters to server, get reply, and re-render appropriate cards

Or, remove filter pane from these views.