Open mvuckovic opened 4 months ago
github-actions[bot]
commented
4 months ago 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.
jonaslagoni
commented
4 months ago 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 🤔
github-actions[bot]
commented
1 week ago This issue has been automatically marked as stale because it has not had recent activity :sleeping:
It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.
There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.
Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.
Thank you for your patience :heart:
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/rejectedIt seems V3 currently only supports a single reply address object. Is there any recommended way I could achieve this with the current spec?
Thanks :)