fix: openapi edge case for empty payloads #1383
Closed
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.
Motivation and Context
The generated
wundergraph.openapi.json
specification doesn't currently handle mutations that have no input. The requestBody shouldn't be required per the OpenAPI 3.1.0 docs, but theopenapibuilder
code currently assumes that we always have an input.Now, for mutations that have no input, instead of of a payload that shows as an empty object...
We have a payload that just shows as empty and non-required:
This will correct the generated spec for the small subset mutation operations that don't consume an input.
Marketing Changelog
OpenAPI Generated Spec now formats POST's with empty payloads correctly
Checklist
make test