Skip to content
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

extend error message with name of message that is missing the name or msgIdentifier #197

Open
AceTheCreator opened this issue Mar 22, 2023 · 4 comments

Comments

@AceTheCreator
Copy link
Member

When using the nodejs-template to generate code and in one of your messages, you failed to pass the name or messageId. When running the code, you get the error Message Rejected. msgIdentifier "name" does not exist but it does not tell you which of the message in your spec is missing the required property. So if you have a lot of messages in your spec, it will be quite hard for you to figure out which message is missing the property

@github-actions
Copy link

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.

@derberg
Copy link
Member

derberg commented Mar 28, 2023

yeah, we need a validation in place that will simply check if that required identifier is in the asyncapi document that one want's to use, and if not, block generation with proper message.

I'm only worried for those that do not care about validation, and cannot modify their documents to add identifiers, what in their case. We should probably allow to disable validation?

kaushik-rishi pushed a commit to kaushik-rishi/nodejs-template that referenced this issue Aug 23, 2023
@ibishal
Copy link

ibishal commented Jun 19, 2024

@derberg is this issue still valid ?

Copy link
Member

derberg commented Jun 19, 2024

yup it is, feel free to pick it up

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants