-
-
Notifications
You must be signed in to change notification settings - Fork 238
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
Integrate new ParserAPI #825
Comments
This is actually blocking templates from using the new Modelina I could reparse everything again, but that does not seem right to do either 😄 Any suggestions how to fix it? |
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 ❤️ |
We should integrate new ParserAPI in Generator but with fallback compatibility with old one, solution described in the asyncapi/parser-js#585:
apiVersion
with possible values,v2
andv1
-v1
should be default valueparser-js
version in generatorThe text was updated successfully, but these errors were encountered: