-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unlimited Restricted Airspace Displayed as FLNaN #756
Comments
@Fechulo @erikquinn That is because it's trying to parse a string 'Unlimited' which is obviously, not a number. This should, hopefully, be an easy fix. Should it display |
never mind, I found it. |
@Fechulo is this the first you noticed this issue? From what I can tell, this much have been an issue for quite a while. Oh well, it's going to be addressed for v3.2.0. |
@n8rzz I believe it should just display 'UNL'. This was definitely working before v3 but I'm not sure when it stopped working. There's very few airports in the game that have restricted airspace with an unlimited ceiling, so I found it today while working on El Paso Intl. |
@Fechulo right on, I think there were two airports that came up when I searched. I'm sure I got a little jumpy refactoring and something was missed. In fact, thats my assumption here. Good news is that there are now specific tests for this case, so once the bugfix is completed we will know that this case is covered with tests. |
@n8rzz does |
@erikquinn parseFloat(Infinity) -> Infinity
parseFloat('Infinity') -> NaN As far the FL and the UNL, that is already implemented within the const height = (area.height === Infinity ? 'UNL' : 'FL' + Math.ceil(area.height / 1000) * 10); |
Resolved by #755. Closing. |
When the ceiling of restricted airspace is unlimited, it is displayed as FLNaN in the game, instead of UNL. It can be seen at UUDD:
The text was updated successfully, but these errors were encountered: