You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* @param {String} [options.templateParams] Optional parameters to pass to the template. Each template define their own params.
to this:
* @param {Object} [options.templateParams] Optional parameters to pass to the template. Each template define their own params.
Reason being is, in the constructor body, templateParams is going to be used for Object.keys. If string is used with Object.keys, it will result in the character indices instead.
>Object.keys("{}")Array["0","1"]
I can help create a pull request, if this issue is indeed valid. Let me know if I need to provide more information. Thanks!
Attach any resources that can help us understand the issue.
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. Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.
Describe the bug you found in AsyncAPI Docs.
Hello!
I want to propose line change from this:
generator/lib/generator.js
Line 80 in 76c106b
to this:
Reason being is, in the constructor body,
templateParams
is going to be used forObject.keys
. If string is used withObject.keys
, it will result in the character indices instead.I can help create a pull request, if this issue is indeed valid. Let me know if I need to provide more information. Thanks!
Attach any resources that can help us understand the issue.
This contradicts with this line:
generator/lib/generator.js
Line 125 in 76c106b
Code of Conduct
The text was updated successfully, but these errors were encountered: