NASA-AMMOS / NASA-AMMOS/plandev
Versioning for command expansion rules
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 128
- Forks
- 33
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 12
Description
winner
https://jira.jpl.nasa.gov/browse/AERIEQS-277
Low
It can be difficult to tell command expansion rules apart since it is possible to define more than one rule for an activity type using the same command dictionary and model ID. It would be useful to be able to provide a versioning field which would be displayed in the list of expansion rules, and/or the ability to give a rule a custom name in addition to the assigned rule ID.
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
No files, tests, or entry points are named. Start by locating the command expansion rule model and the list where expansion rules are displayed, then review the linked Jira item for the intended scope. Done should make rules with the same command dictionary and model ID distinguishable through a displayed version or custom name.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100