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
When using this template to generate your code, by default, it uses name as the messageIdentifier but if you use AsyncAPI v4 and above, there's already support for messageId, which means we should be able to use messageId as an identifier. So when generating your code, I suggest we add an optional additional flag that tells the generator to not use name but instead messageId.
Example @asyncapi/nodejs-template -o output -p server=production messageIdentifier=messageId
The text was updated successfully, but these errors were encountered:
When using this template to generate your code, by default, it uses
name
as the messageIdentifier but if you use AsyncAPI v4 and above, there's already support formessageId
, which means we should be able to usemessageId
as an identifier. So when generating your code, I suggest we add an optional additional flag that tells the generator to not usename
but insteadmessageId
.Example
@asyncapi/nodejs-template -o output -p server=production messageIdentifier=messageId
The text was updated successfully, but these errors were encountered: