fix: Expose peer contexts from app connections#190
Merged
Conversation
Return side-specific connection handles from AgentApp.connect and ClientApp.connect so connection-scoped code can call the peer through .client or .agent outside request handlers. Add symmetric onConnect hooks for app-owned connection setup, route connectWith through the same handles, and keep the exposed contexts backed by the shared underlying ConnectionContext.
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
1 participant
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.
Return side-specific connection handles from AgentApp.connect and
ClientApp.connect so connection-scoped code can call the peer through
.client or .agent outside request handlers.
Add symmetric onConnect hooks for app-owned connection setup, route
connectWith through the same handles, and keep the exposed contexts backed by
the shared underlying ConnectionContext.