-
-
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
Disable the generators that are not yet supported in V3 #979
Comments
Hi @Amzani Can I work on this issue? |
Sure @devilkiller-ag please take it |
Hi @Amzani, I noticed there's no indication of which generators are supported. Do you think it would be a good idea to include an array listing the supported generators? |
@kalpesh-d it's in the description |
Is this issue is fixed now? |
Yes it is currently being resolved and is near finishing. |
Sorry @Amzani, I got busy with my exams this week, I was planning to resolve this today. @kalpesh-d This issue was assigned to me. You should have asked here before starting your work on this. I am happy that you resolved this issue, but kindly keep in mind to ask the assignee before working on it out of the blue. |
@devilkiller-ag, I apologize for not checking with you first. |
* fix: Disable unsupported generators for AsyncAPI V3 (#979) * Refactored GeneratorModal for AsyncAPI V3 support and removed [TRACKING_LINK] * fix lint errors * fix warning --------- Co-authored-by: samz <[email protected]>
Some generators don't support yet V3
Current behavior
In V3 document (example) not supported generators are displayed even though they are not supported.
Expected behavior
For a better Developer Experience(DX):
Tracking link: #980
Note: Currently there is a bug in the Doc generation for V3, the fix is WIP asyncapi/cli#1200
The text was updated successfully, but these errors were encountered: