-
Notifications
You must be signed in to change notification settings - Fork 533
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Discriminator mapping refs (anyOf) & callback refs not processed #2086
Comments
The relative refs issue in callbacks & parameter examples can be worked around by changing the ref path to be relative from base directory, instead of current directory. But the Discriminator mapping ref issue breaks codegen, it is not able to resolve the Type. And creates some |
@frantuma any updates on the PR for this issue? |
These issues are not present in the npm swagger-parser library. |
@frantuma / @gracekarina, Can you help check if #2087 help solve this as expected? |
ponelat I don't see any active changes to this repo, is this not actively maintined? Any help on this would be useful. |
fixed in #2087 |
When relative paths are used in discriminator mappings (anyOf) & callbacks the references are not processed.
Discriminator Mapping Ref sync issue:
In this case post the parsing the anyOf schemas becomes
#/components/schemas/adoption_request_for_bird
but the disciminator mapping still remains as../components/schemas/adoption_request_for_bird.json
. However the same works forOneOf
.Callback Ref issues:
In this case the
payload
schema is incorrectly searched from theopenapi.json
base path instead of the relative path from the callback. Also this (looking in base path instead of relative path) seems to occur for parameter examples too.The text was updated successfully, but these errors were encountered: