-
-
Notifications
You must be signed in to change notification settings - Fork 171
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
Better UX support for using --use-new-generator flag. #1540
Comments
@Souvikns I believe we would need to consider multiple versions as more than two as time comes, WDYT? |
Currently the error message that I am getting when you try to generate from a template which needs the new generator and I don't use the
Yeah I think so but if with newer genererator versions we can stop giving support for the old one, I think we need to do this as long templates are still relying on the older version of the generator. |
I tried running it on wsl bash on my computer, and I am getting what @derberg is getting so this is the happening only in bash. |
--use-new-generator
scares me 😄 and generating without it, for template that needs new generator just givesGenerator Error: Installation failed
. Weren't you able to intercept the error, that would say that template do not support old generator, and in the error you could drop some good info for the user? like to use the flagalso look at this strange behavior with logs, when I use the
--use-new-generator
flag:my test command:
asyncapi generate fromTemplate https://raw.githubusercontent.com/asyncapi/spec/refs/heads/master/examples/streetlights-kafka-asyncapi.yml https://github.com/derberg/html-template#bumphtml --force-write --use-new-generator -o dupa
that uses asyncapi/html-template#615Originally posted by @derberg in #1388 (comment)
The text was updated successfully, but these errors were encountered: