Releases: asyncapi/generator
v0.34.1
v0.34.0
0.34.0 (2020-03-18)
NOTICE:
This release introduces a new name of the package. Instead ofasyncapi-generatorwe now release to NPM under@asyncapiscope, so the package you should now use in your dependencies is@asyncapi/generator
Features
v0.33.0
Changes in this release:
- Changed Node.js base image in Dockerfile to version 12 on the
nodejstemplate (#244). Thanks, @jorge07 🔝 - Added the "Sponsor" button on Github ❤️
- Added GitHub Actions-powered stale bot and a welcome message for new contributors 👋
- Upgraded JS parser and made it register the optional schema parsers (#247) 💪
v0.32.0
In this release, we added support for server variables in the Node.js template and added a bunch of recipes for template authoring.
Aside from these new features, a bug with template installation when using the library as a module has been fixed.
v0.31.0
Templates are now transformed into packages. In other words, templates dependencies are managed separately. Each template has now a separate package.json to manage its dependencies. You should get package.json for your templates too. Check out a sample package.json for nodejs template.
The generator, automatically triggers template dependencies installation, if node-modules is not present in the template's directory. To perform additional installation during generation, pass --force-install flag.
Related issue #214.
v0.30.0
Git support is now enabled. When you generate files:
- To non-empty directory, you get an error with information that you can lose some of your work that can be overwritten.
- To a directory in a Git repository, you get an error that you might lose some of your work but only in case you have some unstaged changes, and the directory is not in .gitignore.
We also introduced a new flag in CLI called --force-write (it is also supported on a library level) and it will allow you to ignore rules provided by this feature.
