NASA-AMMOS / NASA-AMMOS/AIT-Core
Revisit PrimitiveType and None Name
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 56
- Forks
- 35
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 3
Description
Revisit the PrimitiveType name and format handling in light of #472. Seems like it would be better for PrimitiveType to be very strict about what it requires for names. Additionally, a _format of None doesn't seem like it makes sense for PrimitiveType. That seems more like a hack to support the current poorly thought out inheritance structure.
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
Start by reading issue #472 and tracing the PrimitiveType implementation and its inheritance relationships. Determine the intended strict name requirements and how _format=None is currently used. Done should mean the naming and format behavior are explicitly resolved without relying on the questioned inheritance workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100