Lukasz Gornicki
Lukasz Gornicki
we have green light to pull that repo it: https://github.com/asyncapi/generator-react-sdk/issues/253
please indicate here first how you plan to solve it
ok, first please work on migrating AsyncAPI document to v3, and share results here to make it easier for you, here you have [v2](https://github.com/derberg/python-mqtt-client-template/blob/v1.0.0/test/fixtures/asyncapi.yml) example migrated to [v3](https://github.com/derberg/python-mqtt-client-template/blob/main/test/fixtures/asyncapi.yml)
you can take this up @mitaliiiiii
`packages/components/readme/` makes lots of sense, might be `template/client/websocket/javascript/components/readme/` is not really needed. I bet that once all components are created, we will see all are reusable and you will endup...
yup, in theory majority of readme files, for clients for any protocol, will be looking almost the same, with the same headings, etc, so having them in `packages/components/readme` is best....
> We'll start by adding deprecation warnings to all Nunjucks-related features what do you mean? in case of cli.js it is easy as we will drop a message in cli,...
hey folks, be patient here 🙏🏼 there are many PRs that we need to review, also test runs are not fast. If you wanna speed up, make sure you run...
also, folks please do not address any fixes or anything in `cli.js` file