-
-
Notifications
You must be signed in to change notification settings - Fork 98
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
parseFromUrl does not resolve relative references #504
Comments
@jonaslagoni just to be sure, this is |
@derberg that would make sense yes. |
🎉 This issue has been resolved in version 1.16.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This issue has been resolved in version 2.0.0-next-major.18 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Describe the bug
Given the use of
parseFromUrl
I would expect that if the remote document contained relative references, they would be resolved based on the URL passed toparseFromUrl
🤔How to Reproduce
Given a reference such as
"$ref": "./components/parameters.json#/server_id"
in an AsyncAPI document located athttps://raw.githubusercontent.com/org/repo/main/asyncapi.json
I would expect it to fetch the parameter fromhttps://raw.githubusercontent.com/org/repo/main/components/parameters.json#/server_id
instead of trying to fetch it locally on the machine.The text was updated successfully, but these errors were encountered: