-
Notifications
You must be signed in to change notification settings - Fork 907
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
refactor(experimental): make abort signals mandatory in subscriptions #1640
refactor(experimental): make abort signals mandatory in subscriptions #1640
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @steveluscher and the rest of your teammates on Graphite |
c3c4120
to
40b745e
Compare
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.
9e008fd
to
d9d004b
Compare
40b745e
to
e3fbbcf
Compare
d9d004b
to
679b719
Compare
e3fbbcf
to
b0b7086
Compare
679b719
to
d4fd0cc
Compare
b0b7086
to
7ea1c8d
Compare
d4fd0cc
to
e8a1183
Compare
7ea1c8d
to
dbe3e48
Compare
e8a1183
to
d838c45
Compare
dbe3e48
to
24494cb
Compare
d838c45
to
c72a627
Compare
24494cb
to
063af49
Compare
063af49
to
7f4ee8c
Compare
Merge Activity
|
🎉 This PR is included in version 1.78.6 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Because there has been no activity on this PR for 14 days since it was merged, it has been automatically locked. Please open a new issue if it requires a follow up. |
Summary
OK listen. We're all adults here. That being said, not having a strategy for cancelling your RPC subscriptions makes everything really complicated and leaves your code prone to leaks.
AbortSignal
is now a mandatory argument tosubscribe()
.If you really want to launch your subscriptions without any cancellation strategy you can still do this:
We won't judge you.
Test Plan