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
Swagger unmarshaljson #113338
Swagger unmarshaljson #113338
Conversation
/triage accepted |
Since we're now using the experimental json code to deserialize spec.Swagger, we should rather use UnmarshalJSON since this has a much lower CPU overhead.
f955fa5
to
5be7430
Compare
Remaining usages of |
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: apelisse, liggitt 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 |
/retest |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Use
Swagger#UnmarhsalJson
rather thanjson.Unmarshal
to deserialize OpenAPI spec since there is a 2x overhead withjson.Unmarshal
now that we're using the experimental json deserializer.Which issue(s) this PR fixes:
Follow up from #112988
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: