As a restaurant manager
I want to create a new reservation when a customer calls
so that I know how many customers will arrive at the restaurant on a given day.
Acceptance Criteria
1 The /reservations/new page will
have the following required and not-nullable fields:
First name:
Last name:
Mobile number:
Date of reservation:
Time of reservation:
Number of people in the party, which must be at least 1 person.
display a Submit button that, when clicked, saves the new reservation, then displays the /dashboard page for the date of the new reservation
display a Cancel button that, when clicked, returns the user to the previous page
display any error messages returned from the API
2 The /dashboard page will
list all reservations for one date only. (E.g. if the URL is /dashboard?date=2035-12-30 then send a GET to /reservations?date=2035-12-30 to list the reservations for that date). The date is defaulted to today, and the reservations are sorted by time.
display next, previous, and today buttons that allow the user to see reservations on other dates
display any error messages returned from the API
3 The /reservations API will have the same validations as above and will return 400, along with an informative error message, when a validation error happens.
seed the reservations table with the data contained in ./back-end/src/db/seeds/00-reservations.json
jaredtyrel
commented
1 year ago
As a restaurant manager I want to create a new reservation when a customer calls so that I know how many customers will arrive at the restaurant on a given day.
Acceptance Criteria
1 The /reservations/new page will have the following required and not-nullable fields:
2 The /dashboard page will
3 The /reservations API will have the same validations as above and will return 400, along with an informative error message, when a validation error happens.