Feat/message send router#106
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
701f3d0 to
d2f23cf
Compare
d2f23cf to
af457ca
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add AsyncFast message send router
Description
Summary
This PR adds reusable routing support for AsyncFast message send operations and refactors channel routing to share the same underlying route-matching logic.
Changes
Routerutility.ChannelRouter, keeping channel resolution behavior centralized.ChannelNotFoundErrorinto shared routing utilities so it can be used by both receive and send routing.MessageSendRouter, an async context manager that routesmessage.sendevents to different send backends based on event address.Why
AsyncFast already supports address-based routing for inbound channels, but outbound message sends previously had to be wired to a single send backend. This makes it possible to route different outgoing message types to different AMGI send implementations while preserving lifecycle management through async context managers.
Testing
MessageSendRouterdefault routing.