when the same component used in two different places in two different apis then parser fails - #1627
Closed
ptrsd wants to merge 1 commit into
Conversation
… apis then parser fails
ewaostrowska
force-pushed
the
test-cases-for-ClassCastException-when-resolving-external-refs-more-than-once
branch
from
August 10, 2026 13:45
4606548 to
8102660
Compare
Contributor
|
Thanks for reporting this @ptrsd . I agree that the parser should not throw a raw However, I don't think the tests in this PR describe valid OpenAPI behavior and I would also prefer to have it reported as an issue if this problem still occurs as I am unable to merge the PR anyway if the tests are failing. I am closing this PR. If the issue persists please report it as an issue according to the current template |
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
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.
Hi, I'm getting ClassCastException when the same parameter from $ref is used in different places in different APIs. In this PR I've added a test case for this problem.
Exception: