t-persson / mira Goto Github PK

By choosing recipes, a weekly menu should be created for the user. A random menu could be created based on the content of the fridge or based on different labels/categories.

• Frontend weekly menu
• Backend weekly menu - t-persson/babylon#2
• Search filter for categories/lables or based on fridge items - t-persson/babylon#2

According to GDPR a user should be able to choose to be removed at any time. The user should have the option to remove the personal data that has been previously submitted to the application.

t-persson/babylon#5

• Add a delete button to remove a user and linking user information

A shopping list could be created maybe by choosing some recipes in the app and then check what is in the fridge already. If items are missing these could be added to a shopping list.

• Shopping list frontend
• Shopping list backend - t-persson/babylon#3
• Button to add ingredients from recipes
• Add separate items to the shopping list - t-persson/babylon#3
• Delete items from the shopping list - t-persson/babylon#3

A logged in user should have digital fridge to which items can be added. This can then be used to search for matching recipes with ingredients.

• Add a digital fridge
• Add backend for a digital fridge - t-persson/babylon#4

An item can have for example the following attributes:

• Name
• Date added
• Best before date
• Amount

I was thinking that a logged in user can have a profile or its own space where the actions demanding authorization can be placed. Add recipe, the fridge, weekly menu, delete account, update user information (username, email and change password), private shopping list etc.

When creating a new recipe the user needs to add an author. This should be the logged in users username and to be added by default.

A user should have a username to display instead of an email address in the app.
Privacy: This will avoid a user to get spam emails or contacted by unknown people if they do not want to. An email address can be connected to a specific user and is therefore a personal identification attribute (GDPR)

• Update database - Fixed here: t-persson/babylon#1
• Update the register page
• Update userInfo to be the username instead of the email

Create functionality to reset the current password. One way to do this is by sending an email with a unique token which expires in a certain amount of time. Another can be to use a phone number and send a code with text or something.

• Frontend forgot password
• Backend forgot password - t-persson/babylon#10

When a user adds a recipe to the application, the option should be there to choose to not share it with others if the user does not want to.

According to GDPR, we need to have a cookie acceptance bar or otherwise inform the user that we are using cookies to store session information. The user should be able to opt-out and anonymously use or not use the web page, especially if it is made public.

• Create a cookie acceptance pop-up

When clicking the logout button it is still shown until the page is refreshed. Steps to reproduce:

1. Login as a valid user
2. Click the logout button

Create the functionality to register as a user to the application. A user should be connected to a unique email address for example.

• Frontend register page
• Backend register
• Add a password policy:
  - Length: 8 - 20 chars
  - Min 1 capital letters
  - Min 1 regular letters
  - Min 1 number
  - Min 1 special character
• Validate email address as email address
  - Check that there is only one "@" in the string