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
I'm trying to document MQTT Request/Response pattern where a single Request can result in multiple channel/message replies, something similar to AWS IoT Core Shadow/shadow/get, /shadow/get/accepted, shadow/get/rejected
It seems V3 currently only supports a single reply address object. Is there any recommended way I could achieve this with the current spec?
Thanks :)
The text was updated successfully, but these errors were encountered:
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.
In the current version you would have to create multiple operations where each results in a single reply 🙂 When the feature was created we never discussed that a single operation should be able to result in multiple addresses on a single operation, either through channel or reply 🤔
Hello!
I'm trying to document MQTT Request/Response pattern where a single Request can result in multiple channel/message replies, something similar to AWS IoT Core Shadow
/shadow/get
,/shadow/get/accepted
,shadow/get/rejected
It seems V3 currently only supports a single reply address object. Is there any recommended way I could achieve this with the current spec?
Thanks :)
The text was updated successfully, but these errors were encountered: