max_stops query parameter addition#11
Conversation
added max_stops
|
Hey, My apologies, but I'm on mobile. Could you describe how you made max_stops possible? Thanks a lot for your awesome work! AWeirdDev |
Field 5 of the FllightData protocol buffer object accepts an integer for number of stops on each defined flight. The values according to the selectors on the UI (determined after decoding protocol buffers string) are as follows:
Higher numbers are allowed (15 for example) but don't seem to have any impact. Implementation was achieved by adding the optional integer for field 5 to the protobuf definition and recompiling: After that, was just adding support for it in your core: As well the filter to fill it for all FlightData objects, if it's supplied: Any other UI options, such as bags, should be trivial to add in similar fashion. |
Added optional ability to specify max_stops for flight data search along with
example.pyreference usage script.Acceptable values are 0, 1, 2 or undefined for "all flights".