Fix OpenAPI schema validation issues #18161
Open
+81
−179
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cconard96
changed the title
cconard96
force-pushed
the
fix/openapi_schema
branch
from
e152555
to
0af0550
Compare
orthagh
approved these changes
Oct 30, 2024
trasher
requested changes
Oct 30, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Checklist before requesting a review
Description
The OpenAPI schema has some validation issues according to the online Swagger editor. None of the validation issues actually seem to affect the Swagger UI display, but I guess some tools could have trouble parsing it. For example, the online Swagger editor doesn't seem able to generate clients based on the schema.
Fixes #18158