• Modify the recipe detail view to display the recipe details if the recipe is public or the user is the owner
• If the user is the owner of the recipe, provide a link or button in the recipe detail view that leads to a form for adding new food to the recipe
• In the controller, retrieve the recipe and check if the user is the owner or if the recipe is public before rendering the recipe detail view
• Test the recipe detail view to ensure that it is only displayed for public recipes or the owner and that the link or button to add new food is only displayed for the owner

• Determine the links that should be included in the navigation menu
• Create a partial for the navigation and include/render it In the layout file
• Use the link_to/button_to helper to create a link for each item in the navigation menu
• Test the navigation menu to ensure that it is displayed correctly and the links work as expected

• Create the views
• Design the database schema and create a migration to add the necessary tables or columns to store the shopping list information
• Create controllers and models
• Write any necessary tests to ensure that the shopping list feature is working as expected
• Test the shopping list feature to ensure that it is working as intended

This should lead to the recipe details route and display a list of all public recipes ordered by the newest as in the wireframe.

• Create Views
• Create Controllers and model
• Test

• create food lists view
• Create a model and migration to store the list of food and their quantities
• Create a controller and action to retrieve the list of food and their quantities from the database and pass it to the view
• In the view, display the list of food and their quantities using an appropriate HTML element
• Test the food list to ensure that it is displayed correctly and displays the correct information

Note 🔖

This project is being developed by:

• Baraka Danny
• Muskan

Link to the Project distribution Kanban board

Happy Coding 🥂

• Set up Devise in the Rails app
• Create the necessary routes for the login and signup pages
• Generate the controllers and views for the login and signup pages
• Test the login and signup functionality to ensure that users can successfully create an account, log in, and log out

This should lead to the recipe details route and only the owner can delete a recipe

• Create a model and migration to store the recipe information
• Create a controller and action to retrieve the list of recipes from the database and pass it to the view
• In the view, display the list of recipes using an appropriate HTML element
• Test the recipe list to ensure that it is displayed correctly and displays the correct information

• Write RSpec tests for the selected parts of the application

• Identify N+1 queries in the application using tools such as the bullet gem
• Test and implement different solutions to eliminate N+1 queries, such as:
  - Eager loading with includes
  - Manual preloading with preload, eager_load, or joins
  - Database-level optimization with indexes and proper database design
  - Query optimization
• Test the application to ensure that N+1 queries have been successfully eliminated