oxidecomputer / oxidecomputer/progenitor
non-required and nullable parameters are conflated
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1k
- Forks
- 136
- Avg merge
- 8h 36m
- Merged PRs (30d)
- 14
Description
Currently non-required and nullable parameters are treated as redundant and interchangeable when they aren't quite. A parameter, foo, might be required and nullable meaning that the server expects a value for foo but that value could be null. This is different than a non-required parameter whose value may not be null where foo=null would be invalid.
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 file, test, or entry point is named in the issue. Start by tracing how the Rust generator represents and processes required and nullable parameters, then identify where those states are conflated. Done means required nullable parameters accept null while non-required non-nullable parameters reject foo=null, with coverage for both cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100