-
Notifications
You must be signed in to change notification settings - Fork 39.8k
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
Cleanup the replaceKeys and setElementOrder code in strategic merge patch #46543
Comments
/assign |
@mengqiy can you please add sig labels to issues you create? /sig api-machinery |
/sig cli |
Can we close this issue @mengqiy |
Probably not. Please leave it open. I will address it when I have some cycles. |
Issues go stale after 90d of inactivity. Prevent issues from auto-closing with an If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Comments in replaceKeys:
Comments in setElementOrder:
https://reviewable.kubernetes.io/reviews/kubernetes/kubernetes/45980#-KlQrynxqa6fwPdcLbeh
https://reviewable.kubernetes.io/reviews/kubernetes/kubernetes/45980#-KlQsAHkxPOz_MIUFler
https://reviewable.kubernetes.io/reviews/kubernetes/kubernetes/45980#-KlQn7QltA-Wkwh6Q_aN
These comments are all about code style and refactoring.
The text was updated successfully, but these errors were encountered: