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
For now, only the first message of the operation or channel is supported, others are discarded.
All messages should be supported by multiple send and receive function (one per message). It will require to listen to a channel and separate depending of the message.
PR #332 implements the send side: when an operation (or its channel) declares more than one message, a dedicated SendAs<Op>For<Message> function is generated for each, so every message can now be sent (previously only the first was usable). It also fixes a latent non-determinism in Channel.GetMessage that could produce unstable/non-compiling code for multi-message channels.
The receive side is not yet covered and this issue stays open to track it. The chosen per-message API (SubscribeToXForA / SubscribeToXForB) collides with the controller's address-keyed subscription map (one subscription per channel address, with an "already subscribed" guard), so it needs a rework of subscription management plus the agreed try-each-until-valid message discrimination. The subscribe side currently still handles the first message only.
The send side shipped in #332: when an operation (or its channel) declares more than one message, a SendAs<Op>For<Message> function is now generated for each, so every message can be sent (previously only the first was usable). It also fixed a latent non-determinism in Channel.GetMessage.
The remaining receive side is tracked in #333 (per-message subscribe functions + try-each-until-valid discrimination + the subscription-map rework it requires). Closing this issue in favor of that focused follow-up.
Activity
[-]AsyncAPI v3: Support multiple messages[/-][+]AsyncAPI v3: support multiple messages[/+]feat(v3): generate a send function per message for multi-message oper…
lerenn commentedon Jun 12, 2026
PR #332 implements the send side: when an operation (or its channel) declares more than one message, a dedicated
SendAs<Op>For<Message>function is generated for each, so every message can now be sent (previously only the first was usable). It also fixes a latent non-determinism inChannel.GetMessagethat could produce unstable/non-compiling code for multi-message channels.The receive side is not yet covered and this issue stays open to track it. The chosen per-message API (
SubscribeToXForA/SubscribeToXForB) collides with the controller's address-keyed subscription map (one subscription per channel address, with an "already subscribed" guard), so it needs a rework of subscription management plus the agreed try-each-until-valid message discrimination. The subscribe side currently still handles the first message only.lerenn commentedon Jun 12, 2026
The send side shipped in #332: when an operation (or its channel) declares more than one message, a
SendAs<Op>For<Message>function is now generated for each, so every message can be sent (previously only the first was usable). It also fixed a latent non-determinism inChannel.GetMessage.The remaining receive side is tracked in #333 (per-message subscribe functions + try-each-until-valid discrimination + the subscription-map rework it requires). Closing this issue in favor of that focused follow-up.
feat(v3): support receiving multiple messages per operation (#333) (#336