-
Notifications
You must be signed in to change notification settings - Fork 47.3k
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
[be] Remove unused, experimental getCacheSignal API #28706
[be] Remove unused, experimental getCacheSignal API #28706
Conversation
if ( | ||
options && | ||
options.signal && | ||
options.signal !== dispatcher.getCacheSignal() |
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.
This suggests that maybe someone (Next?) is passing the signal returned from getCacheSignal() back to React. But since getCacheSignal isn't exposed, we should be able to just not do that?
@gnoff is this change cool?
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.
confirmed offline that Next is not using this API, so it's safe to remove this
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.
Looks like a bunch of tests need cleanup as well.
d565221
to
084402b
Compare
All cleaned up, landing |
Similar to facebook#28698, this removes the `unstable_getCacheSignal()` API since we don't intend to ship this to stable.
Similar to #28698, this removes the
unstable_getCacheSignal()
API since we don't intend to ship this to stable.