Lukasz Gornicki
Lukasz Gornicki
@quetzalliwrites please approve and merge
I mean, that in theory people in production should never install CLI as `npm install @asyncapi/cli` but `npm install @asyncapi/[email protected]` for example. Same with templates, in production, in pipelines they...
> From my perspective, always better to enable support for new generator version (or optimizer or anything else) and set the older one to deprecate with some period to have...
ok, so we look at a solution to support different version of generator in the CLI, right?
are you, maintainers, will work on it or you have no capacity and rather expect contribution?
ok, but then we're talking about July. So until July nobody will be able to use new AsyncAPI Generator
not doable in generator, thing is that generator recently reached v2 just because of dropping support for some node versions - not really possible to handle such stuff in a...
I'm afraid there might be issues with implementation in https://github.com/asyncapi/cli/pull/1513 as it assumes kinda that v2 is the last major generator version. `--use-new-generator` scares me 😄 and generating without it,...
best would be to reflect the the name of the feature in the command name so `/transfer-issue` and `/ti`
here are examples how workflow for commands in issues look like: - https://github.com/asyncapi/.github/blob/master/.github/workflows/add-good-first-issue-labels.yml - https://github.com/asyncapi/.github/blob/master/.github/workflows/bounty-program-commands.yml so yeah, add new workflow file, with suffix `command` and use `actions/github-script` as above examples...