-
Notifications
You must be signed in to change notification settings - Fork 1
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
some things #7
Comments
thanks @Marcel510 those are both good callouts! I've created #9 to cover the first item. For the second item, I'm still working through more specific validations (and better messaging) for the segment restrictions. If this is defined as: |
I've just checked that and it was defined as: |
Line numbers are a little out of scope for this but better messaging certainly is. Something I have in mind for this is listing the procedure from which this error was found. |
That I'll work as well if that's easier to realise.
Nate Geslin <notifications@github.com> schrieb am Fr., 22. Juni 2018, 17:35:
… Line numbers are a little out of scope for this but better messaging
certainly is. Something I have in mind for this is listing the procedure
from which this error was found.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#7 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AXrs4QOEYn-a9gS3UdCqu1mwY60OBmZIks5t_Q7VgaJpZM4Uzw0N>
.
|
Not sure if the glideslope key is really strictly required, I think it's only needed if you the glideslope angle is not 3.00° otherwise I think it can be left out and it will use the default value of 3.00°.
This may be a valid complaint but I'm not sure. Anyway, it would be great if you could see which line the complaint refers to.
The text was updated successfully, but these errors were encountered: