-
-
Notifications
You must be signed in to change notification settings - Fork 237
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
feat: upgrade @asyncapi/parser
to v2.0.0 and use the new parser-api
#960
Conversation
@asyncapi/parser
to v2.0.0 and use the new parser-api
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.
yes, generator
config prop is needed. Basically imagine we do what @fmvilas mentioned in the other comment, that we make v2 default and release 2.0, without generator
prop in the template, template users instead of clear info "that template is not compatible with 2.0" they will get some parser errors.
great work, probably https://github.com/asyncapi/generator/blob/master/test/__mocks__/%40asyncapi/parser.js can be removed
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 🚀
If there are no new comments before Wednesday feel free to merge on Wednesday
@Florence-Njeri @pratik2315 please have a look on docs changes, your approval is required |
No comments since then, so I'm gonna merge this |
/rtm |
@smoya you can't merge until @Florence-Njeri or @pratik2315 approves |
Yeah, I feel like an adventurer today 😅 |
Co-authored-by: Florence Njeri <[email protected]>
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
/rtm |
🎉 This PR is included in version 1.10.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Replaces #833
Description
Use Parser-JS v2, and new Custom Schema Parsers:
Related issue(s)
Resolves #825
Part of asyncapi/parser-js#481