kubernetes-sigs / kubernetes-sigs/crdify
Add validation loosening awareness to all checks
- Dominant language
- Go
- Stars
- 47
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
Some schema property checks only take into consideration validation tightening as a breaking change, but this isn't always the case.
Depending on how the API is used, there may be cases where you want to be:
- Strict on tightening of validations but not loosening
- Strict on loosening of validations but not tightening
- Strict on both loosening and tightening of validations
Contributor guide
Research direction
Start by locating the schema property checks that currently detect validation tightening and trace how their breaking-change results are combined. Determine how the three requested strictness modes should be represented and applied to every check, then verify that tightening-only, loosening-only, and both-direction behavior are covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100