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

!ADEP Logic: Warning on submission #180

Closed
KHardern opened this issue Jul 21, 2022 · 1 comment · Fixed by #208
Closed

!ADEP Logic: Warning on submission #180

KHardern opened this issue Jul 21, 2022 · 1 comment · Fixed by #208
Assignees
Milestone

Comments

@KHardern
Copy link
Contributor

Part of ADEP logic plan.

On creation or edit of a departure-type flow measure (MDI, ADI, Rate per Hour), user is issued a warning and asked confirm before being able to submit if the ADEP is anything other than a custom value with 4 non-wildcard characters. i.e. can submit without confirming for "EGLL", but multiple values, airfield groups, or use of any wildcard triggers the warning.

Suggested example warning text:

WARNING
You have submitted a departure flow restriction applying to multiple airports. This is usually incorrect as it requires the flow measure to be coordinated across multiple airports. If you have arranged/agreed this with a flow manager to coordinate on the network, you may proceed.

The more likely situation is that you are trying to apply the departure flow restriction separately to multiple airports. For this you must issue separate flow measures

Return and Edit

Ignore warning, issue flow measure

The 'return and edit' option should be first and ideally more prominent.

@KHardern KHardern changed the title ADEP Logic: Warning on submission !ADEP Logic: Warning on submission Jul 25, 2022
@NelisV NelisV added this to the MVP milestone Jul 25, 2022
@github-actions
Copy link

🎉 This issue has been resolved in version 0.29.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants