fix(api): Actually order body params by required vs optional #57244
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closed in favor of manual dereferencing in: #57639
There were concerns about the
jsonrefs
package and it's actually quite simple to manually dereferencePreviously, this ordering silently failed because the request body
schema
we were fetching only had a reference to it's actual key-value pairs. At the very start of the hook, we now replace all references with a lazy lookup object, which will replace the reference with the real key-value pairs when called upon.See
jsonref
documentation for more info