Repository navigation
✨: dedupe ClusterObjectDeployment template and ClusterObjectSet spec into shared content struct #3146
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
✨: dedupe ClusterObjectDeployment template and ClusterObjectSet spec into shared content struct #3146
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Do you think there'd be a way for us to add a test that somehow verifies that all fields in the I'm thinking a unit test that parses the Go code, finds the json field names of the ClusterObjectSetContent struct, and then looks for comments on
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I will handle the automatic field-completeness guard in a separate follow-up PR, keeping the field-specific behavioral regression tests here. The existing tests cover all three current fields, but do not automatically fail when a new content field is added. For the follow-up, I plan to enumerate the struct JSON fields with reflection and require an API-server-backed mutation case for each, so a future field without coverage fails the test. That would verify the generated validation behavior rather than depend on exact Go comment or CEL-expression spelling. |
Uh oh!
There was an error while loading. Please reload this page.