You just accepted a web developer position at Slingshot Airlines!
They were really impressed with the work you did at Concordia Bootcamps. After a conversation with the CEO at the job fair, they hired you on the spot! They have project that they need to ship asap and are confident that you can deliver.
They have a new seat-booking app that is set to be released next week. You were told that most of the work is already done. And that all that remains is just to connect the different pieces to get it working. Because you worked on similar functionality during your bootcamp, you're confident that you can pull it off.
You have been provided with a GitHub repo and little else.
You ask if it is possible to speak to the dev that worked on the project thus far. Nope. Not possible. He left without notice and on bad terms.
Looks like you're on your own...
- When a user navigates to
/seat-selecthe/she is presented with an input to enter the flight number. - With the flight number, make a request to the server for the seating availability on that flight.
- When a response with seating is received, display the seating input as well as the form requesting user's information.
- User selects a seat, enters information and clicks 'Confirm'.
- Contact the server with the data, and wait for a success response to redirect to the
/confirmed.htmlpage. - The confirmed page should display a confirmation message to the user with the info that they entered on the previous screen.
yarn install
This will start the server and make the static pages accessible via their endpoint.
There is a folder called notes that contains possible hints on what to do next...
In order for your project to be considered DONE (passing grade), you should have a working MVP of the app.
- user can select a flight from a dropdown (or any other means you decide to implement).
- user can select an available seat.
- user can enter his/her personal information.
- user can view the flight confirmation page.
- given a
userId(or other user info --up to you), user should be able to view his reservation.
Note that mutated test data will be preserved as long as your server is running. It stays in memory. The changes will only be reset when the server is restarted.
- Connect to the remote db/server to get "live" data. See the
dev_notesfor information on the endpoints. - Create an admin page that displays the seat status for a flight.
- you could reuse the flight selection method you implemented above.
- this page should display a table of all seats, and their status.
- The admin page also displays the name of the user in the seat.
- Each seat also has a link to view the reservation details.