Clear and concise description of the problem

Suggested solution

Alternative

Additional context

Clear and concise description of the problem

Suggested solution

Alternative

Additional context

Auth routes

/api/v1/users/register

• POST: / should register user if required given data is provided
• POST: / should return 400 error if given email is invalid
• POST: / should return 400 error if given email is already used
• POST: / should return 400 error if password length is less than 8 characters
• POST: / should return 400 error if given password doesn’t contain both letters and characters

/api/v1/users/login

• POST: / should login user if email and password match
• POST: / should return 401 error if there is no user with given email
• POST: / should return 401 error if given password is incorrect

/api/v1/users/logout

• POST: / should return 204 status if refresh token is valid

/api/v1/users/forgotPassword

• POST: / should return 204 and send reset token email to user
• POST: / should send 400 if user didn't provide email
• POST: / should send 404 if email doesn't belong to any of users

/api/v1/users/resetPassword

• POST: / should return 204 and reset the password
• POST: / should return 401 if reset token is missing
• POST: / should return 400 if token is expired or user is not found

/api/v1/users/updateMyPassword

Clear and concise description of the problem

Suggested solution

Alternative

Additional context

Clear and concise description of the problem

• Parcel Bundle
• exclude tests when deployed
• different databases for different environment

Suggested solution

Alternative

Additional context

Clear and concise description of the problem

Suggested solution

Alternative

Additional context

Clear and concise description of the problem

Suggested solution

Implement nested booking routes: /tours/:id/bookings and /users/:id/bookings

Alternative

Additional context

Clear and concise description of the problem

Suggested solution

Alternative

Additional context

Clear and concise description of the problem

Suggested solution

Alternative

Additional context

Suggested feature

Add a participants and a soldOut field to each date. A date then becomes like an instance of the tour. Then, when a user books, they need to select one of the dates. A new booking will increase the number of participants in the date, until it is booked out ( participants > maxGroupSize ). So, when a user wants to book, you need to check if tour on the selected date is still available.

Alternative

Additional context

Clear and concise description of the problem

Suggested solution

Alternative

Additional context

Clear and concise description of the problem

To read multi-stage for docker-compose

• https://docs.docker.com/compose/compose-file/compose-file-v3/

Suggested solution

Alternative

Additional context

Clear and concise description of the problem

Suggested solution

Alternative

Additional context

Clear and concise description of the problem

Suggested solution

Alternative

Additional context