-
-
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
Dereference error does not include "title" #561
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. |
Hey thanks for reporting that bug. Line 162 in c962a7e
|
This issue has been automatically marked as stale because it has not had recent activity 😴 It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation. There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model. Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here. Thank you for your patience ❤️ |
It is resolved in the asyncapi/studio#434 |
Describe the bug
The dereferencing parser is not returning
definition.refs.title
, which is expected per ParserError.How to Reproduce
$ref
errors as seen in screenshot, e.g. line 32 and line 39.Problems
paneExpected behavior
A clear and concise description of what you expected to happen.
In the screenshot, one can see that the title referencing line 39 is incorrect. It should be
Token "lightmeasured3" does not exist
.This visual error is because
definition.title
is being used instead ofdefinition.refs[].title
, but more importantly is that I can observe thatdefinition.refs[].title
itself doesn't exist as an output of the parser.The text was updated successfully, but these errors were encountered: