-
-
Notifications
You must be signed in to change notification settings - Fork 241
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
Info/Warning: there's a new version of the X template #330
Comments
This issue has been automatically marked as stale because it has not had recent activity 😴 |
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 ❤️ |
hi @fmvilas I would like to work on this please assign it to me. and also please project me to right direction where should i add the message. |
@AyushNautiyalDeveloper not sure really yet how this should be solved, and if should be solved in general. We work on a PoC now that in few months can answer these doubts |
Reason/Context
By default, npm will not install new versions of a template because it finds it's already installed and skips the installation process. This is a good thing in most cases but can create confusion when someone is trying to use a template and they don't get the latest version features and fixes.
Users can overcome this by executing something like:
ag asyncapi.yml @asyncapi/html-template@latest -o output # Notice the `@latest`
But that's something you do when you really know how the Generator works.
Description
I suggest we add a console.info indicating that a template has a new version available. Something like:
The text was updated successfully, but these errors were encountered: