-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Fix issue where setting defaultOptions
would sometimes break startTransition
for suspense hooks
#11713
Conversation
🦋 Changeset detectedLatest commit: 0827aba The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
size-limit report 📦
|
/release:pr |
A new release has been made for this PR. You can install it with:
|
✅ Deploy Preview for apollo-client-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
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.
Love a one line fix alongside so much additional test coverage 🙌
Fixes #11708
Fixes an issue where setting a default
watchQuery
option indefaultOptions
on theApolloClient
constructor had the potential to breakstartTransition
. When using a default option, thequeryRef.didChangeOptions
check would always returntrue
if the same option were not also passed to the hook directly. Because this returnedtrue
, we'd use a different promise than what React expected for the transition, which ended up showing the Suspense fallback instead of keeping the current UI on screen.This check now takes into account whether the option is defined in the hook options before checking to see if the value changed or not.