-
-
Notifications
You must be signed in to change notification settings - Fork 99
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
fix: report correct range
values in error diagnostics for YAML files
#1126
fix: report correct range
values in error diagnostics for YAML files
#1126
Conversation
🦋 Changeset detectedLatest commit: 416e9d9 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
✅ Deploy Preview for studio-next ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for modest-rosalind-098b67 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for asyncapi-studio-design-system ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Quality Gate passedIssues Measures |
@asyncapi/bounty_team |
/ptal |
@Amzani @magicmatatjahu @KhudaDad414 Please take a look at this PR. Thanks! 👋 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/rtm |
This PR updates
@asyncapi/parser
to version3.2.2
in which forceful normalization of YAML files to JSON format is removed. That change allowsParser
not to be misled anymore into thinking it's dealing with a JSON file instead of a YAML one, therefore paving the way forStudio
to report correctrange
values in error diagnostics for YAML files.Related to asyncapi/parser-js#936, asyncapi/parser-js#1012