What's Changed
π¨ Custom Airports (Breaking)
In the past, AirTrail used a big static file to store all the airports available in the application. This had multiple issues; the obvious one is the size of the file, which not only needed to be embedded in the docker image, but was also sent to every visitor of the website (sounds bad, but browsers are pretty good at caching). It also made updates to the list harder, as it required a new version for each update.
It also limited you to airports that were "official", as there wasn't a way to add your own "custom" airports in the application.
This version uses a new data source for the internal airport list, which can be updated from within AirTrail. If even the new data source doesn't list the airport you want, you can now also add custom airports to the application.
The reason this release is marked as breaking, is that a very small handful (~100/~21000) of airports that were in the old list, are either absent or have changed identifier in the new (updated) source. This means that any flights to or from those few, will break the application. Please open an issue if this affected you.
The biggest ones are:
- Kuwait International Airport
- Jorge ChΓ‘vez International Airport
- Manas International Airport
- Dabolim Airport
- Hazrat Shahjalal International Airport
π Features
- feat: basic flights API by @johanohly in #150
π Enhancements
- feat: new documentation by @johanohly in #149
- feat: add dark map controls by @johanohly in #156
- feat: grey-out airports and routes not connected to the currently hovered airport / route by @johanohly in #157
π Bug fixes
- fix: avoid lowercasing parsed env-var values by @johanohly in #162
New Contributors
Full Changelog: v1.1.2...v2.0.0