-
-
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
Incoming changes for generator #1212
Comments
Research on how and when deprecation should be done: https://github.com/orgs/asyncapi/projects/50/views/1?pane=issue&itemId=67997248 @lmgyuan so from previous discussions, research and past experience, I understand we want to:
|
@derberg Yes that sounds good to me : ) |
Thats sounds good to me ! |
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 ❤️ |
The purpose of this issue is to kida group all different issues that will change generator in coming months.
These are not new issues, some pretty old, some well discussed. So we just need to group them in a kind of roadmap.
ag
cli as we already very well support generator in AsyncAPI CLIDeprecation of AsyncAPI Generator CLI - removing
ag
, not the library #1008nunjucks
rendering engine for deprecation and decide on details (like when will it be removed). We always wanted to remove it to make code less complex and focus fully on react that is much better than nunjucks. Unfortunately I could not quickly find any record of these old discussions. So we will have to do a deprecation with long time for template developers to plan migrationHow about a monorepo 😄 #1044
generator
will still be able to do it, we should still support npm-like template installation. The goal is to focus currently very granular community of code generation (spread across different projects) in one repo, and work together on as many reusable helpers and react components as possible to make templates development and maintenance much easierThe text was updated successfully, but these errors were encountered: