-
Notifications
You must be signed in to change notification settings - Fork 998
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(relay): hide internals of Connection
#3829
Conversation
Connection
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
This looks good. Unfortunately, it is a breaking change so I'll add it to the milestone. We are looking at cutting a new breaking release soon though so we will hopefully be able to merge this in the next couple of weeks.
I've converted it to a draft. We do this for all PRs that are queued to only be merged for the next breaking release. |
@thomaseizinger Is there anything left to do here or is it just waiting for the next release? |
Nothing to do, we are just waiting for the next breaking change which will very likely happen next week! See #3532 for some context on the strategy we are following. |
Can you add a changelog entry for this please? We can then queue it for merging! |
@thomaseizinger Done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Solid, thank you! 🚀
Description
Relayed connections to other peers are created from streams to the relay itself. Internally, such a connection has different states. These however are not relevant to the user and should be encapsulated to allow for more backwards-compatible changes. The only interface exposed is
AsyncRead
andAsyncWrite
.Resolves: #3255.
Notes & open questions
Change checklist