fix(metadata): wrong schema generated if openapicontext set on array #6431
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
|
I don't know if they're needed, but I created new test to cover this bug resolution. |
monitaurus
force-pushed
the
fix-metadata-custom-openapicontext
branch
from
e953cc9
to
a1141bb
Compare
monitaurus
force-pushed
the
fix-metadata-custom-openapicontext
branch
from
a1141bb
to
d57eab4
Compare
|
There's three failing checks, unfortunately I don't know how to fix them, nor if they're linked to this PR. |
|
looks perfect, thanks! |
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.
On a calculated field that returns an array, if we add a ApiProperty to change the type into object, the generated OpenAPI does generate a
"type": "object"but there is also an extra"items": {"type": "string"}.