NASA-AMMOS / NASA-AMMOS/plandev
Include Schema version in SEQ JSON Output from Sequence Editor and Command Expansion
Open
Nobody has claimed this yet.
clipper
sequencing
- Dominant language
- Java
- Stars
- 128
- Forks
- 33
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 12
Description
Schema version should be included in the SEQ JSON output file so that there is a record. This will also add in understanding compatibility issues when schema is updated.
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
Start by locating the Sequence Editor and Command Expansion paths that produce the SEQ JSON output. Determine the schema version source and output format, then verify that generated files record it so compatibility can be assessed when the schema changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100