Changing a recipe makes the diet plan order disturbed.

The meals order should depend on meal type e.g. breakfast, lunch etc. not the order of the time of setting the meals up.

Users should be able to change and choose recipes if they don't like the automatically generated diet plan.
Recipe change should adjust the amount (and energy value) in the background according to the user's needs.

Shopping list elements can be mistakenly deleted and are completely gone. There is no possibility to reverse the action.
To do:
-shopping list item deletion should move it to deleted list
-deleted shopping lists items should be possible to bring back to list

The number of ingredients shown in search results in the recipe form is limited to 5. The query has a both-sided wildcard (at the beginning and at the end) which makes the results very bride. If there are many ingredients related to the one searched for - it may happen that the result doesn't show (if it's a 6th result).

Example:

search for keyword "pomidor"
records in database:

• Sok pomidorowy
• Koncentrat pomidorowy
• Passata pomidorowa
• Pomidory suszone
• Pomidory w puszce
• Pomidor
• Pomidor koktajlowy

Last 2 results won't show up and it's impossible to choose them.

There is still no possibility to add images to recipes.

The form to add recipes should allow images upload. The images should be displayed in recipe/meal preview.
Image uploading feature should be responsible for automatic scaling for thumbnails and full view. It should also convert the image to the most optimal file format and compression (e.g. webp).

Shopping list can only be generated automatically according to a dates range chosen by a user. It can be adjusted afterwards but only for the ingredients already added to the list. It is not possible to add other ingredients if needed and keep all the items to be bought in one place.

If a diet plan contains the same recipes in a couple of following days, a cooking plan (allowing to cook more portions of a dish at once) should be created. It should spare time spent on cooking and make it easier to plan the cooking schedule.

If a shopping list is used by 2 people at once and a shopping list element was already removed by another person it is visible on the list of another person. It is not possible to remove the element by the latter (without reloading the page).

To do:
-shopping list could automatically refresh (using Ajax) to check if there were any changes
-removing an already non-existing element from shopping list should prompt an alert (that it was already deleted! to prevent doubling purchases if app is used by multiple people doing one shopping :) )

Laravel framework needs to be up to date as well as other dependencies.

Algorithm adds large food portions if the users calorie intake is high but the recipe is low in calories.

To do:
-algorithm creating diet plans should prevent adding enormous food portions
-user should be alerted about a large portion at recipe change (if needed)

Users should have the ability to create own recipes.
A custom recipe should only be visible to the user who created it.
Macros should not be calculated for these recipes but users could set them manually.
Any ingredient already existing in DB should be automatically mapped.
Any ingredient not found in DB should be stored as CustomIngredient.
It should be possible to add macros and other nutrients to CustomIngredients - manually by user.

Popular custom ingredients should be regularly added to DB as regular ones (with complete macro and nutrient data) and replaced in all corresponding custom recipes.

(?) A mechanism for automatic scans for popular ingredients should be created. Maybe with a use of GPT to group different names of same ingredients.

Enter button submits the recipe button. It makes a confusion at setting the ingredients up.
It should be blocked (eg. preventDefault) at least while choosing ingredients.

AI can be used to generate recipe ideas.
A user should be able to pass a keyword related to what he would like to eat.

1. A recipe idea should be retrieved from database (if already exists) or query OPENAI-GPT for a new idea.
2. A new idea should be stored in DB.
   If a user asks for a new idea for the same keyword - the process repeats form point 1.
   All keywords should be stored with the count of queries made - to measure what ideas are the most popular.

Business logic needs to be separated from controllers to improve fixing bugs and adding extensions to existing code.