-
Notifications
You must be signed in to change notification settings - Fork 40.7k
feat(validation-gen): add default validation ratcheting support #132236
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(validation-gen): add default validation ratcheting support #132236
Conversation
/triage accepted |
This PR may require API review. If so, when the changes are ready, complete the pre-review checklist and request an API review. Status of requested reviews is tracked in the API Review project. |
bb10a8e
to
1619372
Compare
…nctions This commit introduces a new utility package for the validation generator, encapsulating functions for type handling, including `GetMemberByJSON`, `IsNilableType`, `NativeType`, and `NonPointer`. The existing code has been refactored to utilize these new utility functions, improving code clarity and maintainability. Additionally, the previous unaliasing logic has been removed in favor of the new utility methods, streamlining type validation processes across the codebase. Co-authored-by: Tim Hockin <[email protected]>
Emit equivalence check before emit validators when needed.
1619372
to
ac467d3
Compare
Thanks! /lgtm |
LGTM label has been added. Git tree hash: 6030a46f021544138e37588445c3d05ec02f596a
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: thockin, yongruilin The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind feature
What this PR does / why we need it:
This PR is part of Declarative Validation # ratcheting. It adds the default validation ratcheting support in the generated code.
It includes:
Which issue(s) this PR is related to:
Ref: kubernetes/enhancements#5073
Special notes for your reviewer:
The KEP update has merged: kubernetes/enhancements#5292
The change has been reviewed and merged in the dev repo jpbetz/validation-gen#55
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: