vladbatushkov / flights Goto Github PK

Currently query returns routes with Airports from same city in between.
For example, asking for flights from Bangkok to Moscow you will got route such as:
BKK (Bangkok) -> SIN (Singapore) -> DMK (Bangkok!!!) -> SVO (Moscow)

Autocomplete on "from" and "to" options.
User can use Airport code or city name. Both are valid and append autocomplete.

Currently Query result not fit for Application directly. We need one more layer with computation of all possible combinations for the route spots. For example:

(a -> b -> c) =>
[ (a -> b), (b -> c) ] =>
[ [ flight_1, flight_2], [ flight_3, flight_4, flight_5 ] ] => 
[ [1, 3], [1, 4], [1, 5], [2, 3], [2, 4], [2, 5] ]

Would be awesome to do this Cartesian Product on level of database, not application.

Arrival around midnight. For example, you arrived at 22:00 so you have 2 hours in "this" date and any time of the upcoming "next" date. Search should try to look at "today" flights, but it should also search for flights of the "next" day as well.

Search result are represented as ended list of flights.
Each flights is a card with next information:
Direct/Flights with Stops.
All stops should be mentioned with Cities, Airport codes, Flight Number and Airline (operated flight).
Each flight price should be mentioned. Together with total price.
Departure time, Duration, Arrival time - for each combination of stops.

There is no check on when one plane arrived and then next one departure. Flights output not depends on time at all. Need to provides this feature as part of query filtering.
We need to use formula: 'this departure' + duration of flight + time of transfer (2 hours should be OK) <= 'next departure'. Keep in mind UTC correlation as well.
This task will lead to revisiting of existed Search Query.

Good to have ability to search for direct flights vs flights with stops, 1 stops, 2 stops, for example. Needs to extend params in query to support this feature.

Currently we can find a flight only City-to-City.
Better to improve solution with Airport-to-Airport and mixed-mode: City-to-Airport, Airport-to-City.

Having separated City nodes we can use city locations and simply find distance for Flights Search query usage.
Should contains props: name as STRING, country as STRING, location of type POINT.
We don't really need Country as separated node, but I would be happy if you also can do that.

Format used in query "YYYYMMDD" (20191105)
Calendar picker would be nice feature to have here.