NASA-AMMOS / NASA-AMMOS/plandev
Make Mission Model statically declare ResourceTypes and ResourceSchemas
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 128
- Forks
- 33
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 12
Description
Currently, we're making an assumption that a model's resource types and resource schemas don't change. We should enforce that assumption by having these fields declared statically, similar to how ActivityTypes are statically declared.
Additionally, this will make getting the resource types easier when we upload them after mission model upload, since we will not have to instantiate the model to access them.
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
Locate the Mission Model implementation and the existing static ActivityTypes declarations, then trace how resource types and schemas are accessed during mission model upload. Done means ResourceTypes and ResourceSchemas are statically declared and can be retrieved for upload without instantiating the model.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100