fvalka / aviatorsbot Goto Github PK

Subscriptions should also be added for the da and xwind command.

These could be included in the /add command, for example as /add da loww or /add xwind loww.

Possibly a threshold for the wind change and density altitude change should be preferred. For the xwind the question is how it should be defined, since it is runway dependent. Therefore only a direction and or total wind change could be defined.

On Telegram for Android, all the runs of consecutive digits are rendered as clickable links to dial them as phone numbers. I realise this problem is not of your making, but it's distracting, so it would be nice to prevent it if possible.

A StackOverflow answer that I haven't verified suggests that wrapping <code> around the output could work.

Add a new command which determines the timezone of an airfield (probably based upon its coordinates) and based open this provide the current local time.

Additionally based upon the day the ECET and BCMT can be calculated using an appropriate model for the suns position. For example the following library could be used for calculating the ECET and BCMT:
https://github.com/shred/commons-suncalc

Deploy the Bot to a Kubernetes cluster instead of the single AWS EC2 instance.

Add the highest level of automated tests to the project: End to end tests which connect directly to the live Telegram infrastructure and send the bot commands there and check the bots responses.