-
Notifications
You must be signed in to change notification settings - Fork 56
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
Schema fixes + avoiding duplicate reply begin on mqtt-kafka subscribe stream #872
Conversation
"additionalProperties": false | ||
}, | ||
"additionalProperties": false | ||
"$ref": "#/$defs/options/binding/mqtt-kafka/topics" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure about this one, since we're deliberately using channels
asyncapi concept here, whereas mqtt-kafka deals with kafka-specific topics
instead, so unifying this config causes asyncapi to switch to topics
instead.
"messages" | ||
], | ||
"additionalProperties": false | ||
"$ref": "#/$defs/options/binding/mqtt-kafka/topics" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See feedback on asyncapi options for mqtt-kafka
.
No description provided.