NASA-AMMOS / NASA-AMMOS/plandev
Waiving Constraint Violations
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 128
- Forks
- 33
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 12
Description
Checked for duplicates
Yes - I've already checked
Alternatives considered
No - I haven't considered
Related problems
No related problems
Describe the feature request
Some other mission planning tools have the ability to individually waive constraint violations within a plan. A subset of planners would have permissions to look through constraint violations and waive them. The rationale for the waiver and the user who waived the constraint are stored with the violation. Ideally, the user interface would also have a way to show this information and visualize the constraint violation differently (e.g. turn violation red to gray).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Begin by locating the existing constraint-violation model and planner UI, then determine how permissions and waiver metadata are represented; done should include per-violation rationale and user data, authorized waiving, and a distinct UI presentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- authorization, full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100