Skip to content
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

Open
Marcel510 opened this issue Jun 22, 2018 · 4 comments
Open

some things #7

Marcel510 opened this issue Jun 22, 2018 · 4 comments
Labels
question Further information is requested

Comments

@Marcel510
Copy link
Member

Marcel510 commented Jun 22, 2018

Fail: runways is missing the following required keys: glideslope
Fail: runways is missing the following required keys: glideslope
Fail: runways is missing the following required keys: glideslope

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°.

Invalid value "|S250-" supplied to {icao: String, name: String, body: IProcedureSegmentWaypoint, draw: Array<Array>, rwy: IProcedureSegment, entryPoints: IProcedureSegment}/body: IProcedureSegmentWaypoint/0: IProcedureSegmentWaypoint(IWaypointWithRestriction)/1: WaypointRestrictionType

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.

@n8rzz
Copy link
Member

n8rzz commented Jun 22, 2018

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: ["FIXXA", ["FIXXB", "|S250-"]], then this is a good validation error. If there is an altitude restriction before the speed restriction like: ["FIXXA", ["FIXXB", "A50|S250-"]], then this is a bug on my end.

@n8rzz n8rzz added the question Further information is requested label Jun 22, 2018
@Marcel510
Copy link
Member Author

Marcel510 commented Jun 22, 2018

I've just checked that and it was defined as: ["FIXXA", ["FIXXB", "|S250-"]].
So no bug on your end but still it would be good if there was the line number for easier error spotting.

@n8rzz
Copy link
Member

n8rzz commented Jun 22, 2018

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.

@Marcel510
Copy link
Member Author

Marcel510 commented Jun 22, 2018 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants