oxidecomputer / oxidecomputer/typify
handle multi-type array items that don't map directly to rust tuples
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 898
- Forks
- 114
- Avg merge
- 4h 18m
- Merged PRs (30d)
- 14
Description
A JSON Schema array can have an array of types in the items field. If the maxItems and minItems both match the length of the items array, this type is well-modeled by a Rust tuple. If those cardinalities don't match, we need some more complex type to deal with optional, typed values, and a (potentially unbounded) collection of typed or untyped values past the end of the items array definitions.
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
No source files, tests, or entry points are named. Start by tracing how JSON Schema arrays with an items array are converted to Rust tuples, then determine the expected representation when minItems and maxItems do not equal the number of item schemas; done means optional typed values and remaining typed or untyped values are modeled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100