stackabletech / stackabletech/operator-rs
Optional field handling
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 167
- Forks
- 19
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 9
Description
Currently we ship a lot of CRD fields that are optional because they aren't strictly required for an object to make sense to store, but which are required for that operator to make progress. We could have a macro that performs this parsing automatically (generating the applicable error variants and validated type á la Parse, don't validate).
Ideally this machinery should be possible to extract from #362.
This is a part of https://github.com/stackabletech/issues/issues/198.
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 reading issue #362 and the linked umbrella issue #198 to understand the intended extraction and scope. Identify the existing optional CRD-field parsing approach, then define the macro's supported inputs and generated error and validated-type outputs; done means the machinery can be extracted from #362 and handles the stated optional-field cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100