-
-
Notifications
You must be signed in to change notification settings - Fork 127
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
TypeError: message.id is not a function #748
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. |
We have been encountering the same error since today while using the Docker generator image. |
I have found a way round this to force the @asyncapi/html-template to 0.20.0 before the @asyncapi/react-components next package is referenced.
|
Duplicate of asyncapi/html-template#438 If you personally integrate with this library and parse your AsyncAPI documents before passing them to the library (i.e. use the bundled component without the parser) make sure to use at least v3.0.0-next-major-spec.1 of the parser. |
Should be fixed as of html-template v0.28.4 |
Thanks for the rapid fix @jonaslagoni ! |
@jonaslagoni not sure, but looks like similar problem after update to 49 log
component configuration after template was composed:
|
Similar problem yea, just not related to html template 😄 I should have a fix soon 😅 |
The same here, Error occurs with .lock update to Using TypeError: message.id is not a function |
Should be fixed with the recent version, can you check if it still occurs? |
Renders as expected test specs. I checked rendering on Is it ok, that in new versions of component I see blank page instead of errors? |
@Pakisan please create a new bug report 😄 Most likely error is that the plugin is using a wrong parser dependency version. But might be something else, dont know the context |
This issue has been automatically marked as stale because it has not had recent activity 😴 It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation. There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model. Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here. Thank you for your patience ❤️ |
seems to be fixed please create a new issue if not, with results of error using latest react component |
Description
It looks like the latest changes from eabba4f#diff-ab2dcbe79ad45d341a8591fc20c2b9896235a440f5465b1b8d165b8c733b9a32L62 have caused a breaking change.
When running
npx asyncapi generate fromTemplate asyncapi.yml @asyncapi/html-template -o ./asyncapi --force-write
The following error is show:
Expected result
No error is thrown.
Actual result
Error is being thrown and stops output.
Steps to reproduce
npx asyncapi generate fromTemplate asyncapi.yml @asyncapi/html-template -o ./asyncapi --force-write
Troubleshooting
Tried installing a previous version of the package using the override option with my root package file but this does not seem to take.
The text was updated successfully, but these errors were encountered: