fix(openapi): Invalid type specification #5977
Closed
Conversation
This file contains hidden or 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
DjordyKoert
force-pushed
the
fix/5975-hydra-openapi-spec
branch
from
449d40d to
b8eef21
Compare
DjordyKoert
force-pushed
the
fix/5975-hydra-openapi-spec
branch
from
b8eef21 to
b426ffe
Compare
DjordyKoert
changed the title
|
It seems that multiple openapi got changed to use an incorrect |
|
Closing this since apparently OpenApi 3.1 DOES allow multiple types |
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.
Slight rollback to 3.1 logic for generating OpenApi spec on Hydra.