Checking over the requirements - did we meet them?

[markpereira]

No description provided.

[markpereira]

• (YES) An admin can create planes on the /planes page.
• (YES) A plan has a name, rows, and columns.
• (NO) When a new plane is saved the page should show a seating diagram.
  (Can save plane but no diagram)
• (YES) An admin can create flights on the /flights page. (not creating a plane number for the flight - i.e. plane 4. Plane number is blank on newly create flight. ).
• (YES) A flight has a flight number, origin, destination, date, and plane.
• (NO) When a new flight is saved, the page should show a list with the newest
  date at the top of the list and the number of available seats on the plane.
  (new flight not saving on the home screen ‘all flights’ once created, but when you go to /flights the new flight is there)
• (YES) A user can search for flights on the /search page. (assume this is the /flights page)
  (thought it's the home page not /search)
• (YES)The search page should have an input form for the origin and destination. (but not working)
• (NO) When a user creates a search, the page should show a list of flights with the newest date at the top, (shows flights from search but not newest at top)
• (YES) and include the number of available seats on the flight.
• (YES) When the user selects a flight, we should go to the show page ie, /flights/3. (looks like working but still the # in the url)
• (YES) The plane show page should show a seating diagram with available seats and seats that have been selected, with their names.
• (YES) A user can select a seat.
• (YES) When a seat is saved, the available seats on the /flights page should update. (Looks like working but test again with multiple users using it on the same flight at once.)