-
-
Notifications
You must be signed in to change notification settings - Fork 24
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
Fix x-kubernetes-preserve-unknown-fields
with type array
#314
Conversation
x-kubernetes-preserve-unknown-fields
with type array
8dbe0bd
to
d5bb563
Compare
92ffa3f
to
2dcdaa3
Compare
I dropped my initial test and I believe I changed behaviour of a test that I don't think had the right expectation, a type array for preserve unknown fields feels like it should not be a BTreeMap in this case. |
yeah, i had the same concern. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this looks sensible. Thank you!
Looking at this and cross referencing with the previous PR, I think we probably ought to never map-wrap serde_json::Value for unknown fields. I see we do it in a few more places.
happy to merge on green dco/tests tomorrow 😴
I'll squash my commits to make it easier than going over signing all the other commits :) |
Closes: kube-rs#313 Signed-off-by: Mohammed Naser <[email protected]>
f92b6cc
to
dba295c
Compare
x-kubernetes-preserve-unknown-fields
with type array
x-kubernetes-preserve-unknown-fields
with type array
Closes #313