Resolve infinite recursion and add example test with OpenAPI v3.1 #2833
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.
Resolves #2801.
It turns out, that my desired workaround is no longer necessary, as one can now (since v3.1) have both a description and a
$ref
within a OpenAPI schema.The PR still resolves the potential infinite recursion and gives the schema resolution a small refactor - makes it nicer to read - but thats obviously subjective.
Anyway, I think the testcase can serve as a hint to other users that had similar problems, and it shows that the workaround documented here may no longer be necessary when using OpenAPI v3.1.
As a side note: It also demonstrates, that swagger-api/swagger-core#3900 may potentially be resolved already!