Add capability to define new top-level hierarchies beyond Mission and Aircraft
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 287
- Forks
- 140
- Avg merge
- 6d 14h
- Merged PRs (30d)
- 18
Description
from @jdgratz10:
Desired capability or behavior.
The user is able to extend the variable hierarchy, but aviary currently assumes the only main hierarchies are mission and aircraft. We need to be able to support whatever top level hierarchies the user wants to provide. Create the capability for the user to be able to declare their set of top level hierarchies, potentially but not necessarily (if they don't have any subsystems that require it) including aircraft and/or mission.
For now, we will purely support aircraft and mission because we don't have time to perform this task, however, we need to clearly document current behavior and planned future behavior.
Is your feature request related to a problem? Please describe.
No response
Associated Bug Report
No response
Contributor guide
No contributing guide indexed for this repository
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 does not name files, tests, or an entry point. First map where Aviary defines and consumes the Mission and Aircraft top-level hierarchies, then document the current behavior and planned support for user-declared hierarchies; done means the current limitation and future capability are clearly recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100