-
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 incorrect default devtools config #11969
Conversation
🦋 Changeset detectedLatest commit: f7d7b53 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:
|
Can confirm this fixes the issue. |
✅ 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.
Approved - general question: now that the devtools support multiple clients, does this make any sense at all?
Closes #11707
I made an error and incorrectly copied over the default value to connect to devtools. I forgot the
!
to check if there is already a global client instance 🤦♂️.Regardless, this gives us a chance to re-evaluate the check. Now that Apollo Client Devtools supports multiple clients, we can remove the additional checks for
window.__APOLLO_CLIENT__
when determining how to set the default value. The check will now simply look at__DEV__
to determine whether to connect the client or not when the option is not specified.