8000 Finalize Recipe App by eaesmat · Pull Request #14 · anasbassi/Recipe-App · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Finalize Recipe App #14

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 28 commits into
base: main
Choose a base branch
from
Open

Finalize Recipe App #14

wants to merge 28 commits into from

Conversation

eaesmat
Copy link
Collaborator
@eaesmat eaesmat commented Nov 18, 2022

This PR contains the following changes

  • You should follow the layout of the wireframes provided. You should personalize the rest of the design including colors, typographies, spacings, etc.
  • Login page and registration page:
  • Should be built with Devise.
  • Food list:
  • Should display a list of food added by the logged-in user as in the wireframe (for teams with only 2 people - display also quantity of a given food).
  • Should lead to a form that allows users to add new food.
  • Recipes list:
  • Should display a list of recipes created by the logged-in user as in the wireframe.
  • Should lead to 8000 recipe details.
  • If the user is the owner of the recipe, should allow the user to delete it.
  • Public recipe list:
  • Should display a list of all public recipes ordered by newest as in the wireframe.
  • Should lead to recipe details.
  • Recipe details:
  • If the recipe is public or the user is the owner of the recipe, should display the recipe details as in the wireframe.
  • If the user is the owner of the recipe, should lead to the form that allows the user to add new food.
  • General shopping list view (only for a group that has less than 3 members):
  • Should show the list of food that is missing for all recipes of the logged-in user (compare the list of food for all recipes with the general food list of that user).
  • Should count the total food items and total price of the missing food.
  • Make sure there are no N+1 queries happening.
  • Create a navigation menu that allows users to open all of the pages you created.

Copy link
@muneebulrehman muneebulrehman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi team,

Good job so far! I see you put a lot of effort into this project. However, there are some issues that you still need to work on to go to the next project but you are almost there!

Highlights

  • No linter errors
  • Descriptive PR
  • Good commit history.

Required Changes ♻️

Check the comments under the review.

  • Kindly see the attached video where I demonstrated what issues are still with your application.
  1. Issue with creating the Recipe
  2. Issue with logging out of the application.

Optional suggestions

Every comment with the [OPTIONAL] prefix is not crucial enough to stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better.

Cheers and Happy coding!👏👏👏

Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.

Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.


As described in the Code reviews limits policy you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.

end
end

def create
Copy link
@muneebulrehman muneebulrehman Nov 18, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is some issue with creating the recipes. Kindly refer to this videofor more clarification.

@eaesmat eaesmat closed this Nov 19, 2022
@eaesmat eaesmat reopened this Nov 19, 2022
Copy link
@DammyShittu DammyShittu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @eaesmat and @anasbassi,

Highlights

✔️ Descriptive PR
✔️ Passing linters
✔️ Good branch name

Great work on making the changes requested by a previous reviewer 👏
You've done well implementing some of the requested changes, but there are still some which aren't addressed yet.

Required Changes ♻️

Check the comments under the review.

Optional suggestions

Every comment with the [OPTIONAL] prefix won't stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better. Some of them were simply missed by the previous reviewer and addressing them will really improve your application.

Cheers and Happy coding!👏👏👏

Feel free to leave any questions or comments in the PR thread if something is not 100% clear.

Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.


As described in the Code reviews limits policy you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.

Comment on lines 31 to 44
def create
@recipe = Recipe.new(recipe_params)
@recipe.user_id = params[:user_id]

respond_to do |format|
if @recipe.save
format.html { redirect_to user_recipes_path(@recipe), notice: 'Recipe was successfully created. ✅' }
format.json { render :show, status: :created, location: @recipe }
else
format.html { render :new, status: :unprocessable_entity }
format.json { render json: @recipe.errors, status: :unprocessable_entity }
end
end
end

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • When trying to create a recipe I get this error. The cooking_time seems to be properly permitted but does not appear in the record creation, so it is raising validation issues. Kindly fix that.

    jgue

protect_from_forgery with: :exception

before_action :configure_permitted_parameters, if: :devise_controller?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • Despite being logged out I am still able to visit different pages. Kindly fix this. See example below.

    logged out but can visit foods list page logged out but can visit recipe creation page
    iro rurie

    You can fix this by adding the following helper to this application_controller.rb file. This way only signed-in users can visit certain parts of the app.

    before_action :authenticate_user!
    

Copy link
@danmainah danmainah left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @Team,

Your project is complete! There is nothing else to say other than... it's time to merge it :shipit:
Congratulations! 🎉 🎉 🎉

Highlights

✔️ No linter errors
✔️ Github flow was correctly used
✔️ Good design

Optional suggestions

Every comment with the [OPTIONAL] prefix won't stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better. Some of them were simply missed by the previous reviewer and addressing them will really improve your application.

Cheers and Happy coding!👏👏👏

Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.


As described in the Code reviews limits policy you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants
0