-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
[BUG] $ref to external files not working? #101
Comments
Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request. |
Hi @BenHoopleEmpire - possible duplicate of #48 I'll try your reproduction steps after I take care of #99 |
I'm going to close this bug as i just upgraded intellij, this should be resolved for myself when 99 is resolved |
@BenHoopleEmpire you can clone repo and run
to build new version and test your cases. I have checked, looks like everything is working fine After that install if from |
@BenHoopleEmpire hi! New version is available |
Describe the bug.
this bug deals with the $ref variable not working as expected.
Context:
working with the $ref value is pretty critical for reducing repetition within our docs. I'll give the following basic example:
file: User.yaml
next file Admin.yaml:
Now if i reference Admin.yaml in a components section of an asyncapi.yaml file it fails
i.e.
$ref: '../CommonObjects/Admin.yaml#/Admin'
I know the paths are correct because i've swapped them around and it loads, it is having a hard time with the references inside a file it references.
If this is expected behaviour I'd like to know that, but i feel like this should be possible. I've also looked for any settings but cant find anything that seems to line up with that.
Expected behavior
Expected to see the object being referenced while containing references itself.
Screenshots
How to Reproduce
This is all done in intellij, version 2024.1.4
🥦 Browser
Google Chrome
👀 Have you checked for similar open issues?
🏢 Have you read the Contributing Guidelines?
Are you willing to work on this issue ?
Yes I am willing to submit a PR!
The text was updated successfully, but these errors were encountered: