-
-
Notifications
You must be signed in to change notification settings - Fork 34
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
Regression in v1.3.0 - "info.id is not a function" #357
Comments
Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request. |
That or hardcode the template version in your command 🙂 |
Thanks, if upgrading the CLI is all that's needed, this sounds a lot less serious than I thought. Was just surprised this morning when the command I used yesterday (referencing the default branch) stopped working. Thanks! |
@jonaslagoni we should actually fix https://github.com/asyncapi/markdown-template/blob/master/package.json#L56C21-L56C21 too as generator supports new parser since v1.10.0 @Ernir please never use generator and templates on production like:
or
always make sure you use specific template version as otherwise you get into troubles like you just had more info: https://www.asyncapi.com/docs/tools/generator/versioning always do |
@jonaslagoni just noticed #359. Merged |
🎉 This issue has been resolved in version 1.3.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Describe the bug
When using the markdown template on any document, I receive the error
How to Reproduce
Using any document, such as the simple example:
and running the generator, I receive:
This seems to have been introduced in https://github.com/asyncapi/markdown-template/releases/tag/v1.3.0, prior versions work.
I am using the following version of the
asyncapi
CLI:Expected behavior
I would expect the markdown generator to work as it did prior to 1.3.0 🙂
The text was updated successfully, but these errors were encountered: