Skip to content
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 obscure warning in useFragment when cache.identify returns undefined #12052

Merged
merged 4 commits into from
Sep 4, 2024

Conversation

jerelmiller
Copy link
Member

Fixes #12051

#12020 did some refactoring to useFragment to be more compatible with Rules of React (specifically not writing to ref in render). In the process, useFragment now calls cache.identify directly to ensure that whole data objects passed to from don't trigger rewatches when non key fields change to that object. This change however introduced a regression where invalid identifiers (i.e. cache.identify returns undefined) would show a warning such as:

TypeError: Cannot read properties of undefined (reading '__typename')

This was a result of taking that undefined and passing it as the value to cache.watchFragment, which itself called cache.identify(undefined) and this triggered the warning.

This change ensures that cache.watchFragment forwards undefined to cache.watch as id since it uses ROOT_QUERY as a fallback in that case.

@jerelmiller jerelmiller requested a review from phryneas September 3, 2024 20:00
Copy link

changeset-bot bot commented Sep 3, 2024

🦋 Changeset detected

Latest commit: e712cc9

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@apollo/client Patch

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

Copy link
Contributor

github-actions bot commented Sep 3, 2024

size-limit report 📦

Path Size
dist/apollo-client.min.cjs 39.31 KB (+0.01% 🔺)
import { ApolloClient, InMemoryCache, HttpLink } from "dist/main.cjs" 47.99 KB (+0.02% 🔺)
import { ApolloClient, InMemoryCache, HttpLink } from "dist/main.cjs" (production) 45.57 KB (+0.02% 🔺)
import { ApolloClient, InMemoryCache, HttpLink } from "dist/index.js" 34.41 KB (+0.02% 🔺)
import { ApolloClient, InMemoryCache, HttpLink } from "dist/index.js" (production) 32.29 KB (+0.03% 🔺)
import { ApolloProvider } from "dist/react/index.js" 1.26 KB (0%)
import { ApolloProvider } from "dist/react/index.js" (production) 1.24 KB (0%)
import { useQuery } from "dist/react/index.js" 5.21 KB (0%)
import { useQuery } from "dist/react/index.js" (production) 4.3 KB (0%)
import { useLazyQuery } from "dist/react/index.js" 5.69 KB (0%)
import { useLazyQuery } from "dist/react/index.js" (production) 4.77 KB (0%)
import { useMutation } from "dist/react/index.js" 3.62 KB (0%)
import { useMutation } from "dist/react/index.js" (production) 2.84 KB (0%)
import { useSubscription } from "dist/react/index.js" 4.42 KB (0%)
import { useSubscription } from "dist/react/index.js" (production) 3.48 KB (0%)
import { useSuspenseQuery } from "dist/react/index.js" 5.49 KB (0%)
import { useSuspenseQuery } from "dist/react/index.js" (production) 4.15 KB (0%)
import { useBackgroundQuery } from "dist/react/index.js" 4.99 KB (0%)
import { useBackgroundQuery } from "dist/react/index.js" (production) 3.64 KB (0%)
import { useLoadableQuery } from "dist/react/index.js" 5.07 KB (0%)
import { useLoadableQuery } from "dist/react/index.js" (production) 3.72 KB (0%)
import { useReadQuery } from "dist/react/index.js" 3.39 KB (0%)
import { useReadQuery } from "dist/react/index.js" (production) 3.33 KB (0%)
import { useFragment } from "dist/react/index.js" 2.28 KB (0%)
import { useFragment } from "dist/react/index.js" (production) 2.23 KB (0%)

@jerelmiller
Copy link
Member Author

/release:pr

Copy link
Contributor

github-actions bot commented Sep 3, 2024

A new release has been made for this PR. You can install it with:

npm i @apollo/[email protected]

Copy link

netlify bot commented Sep 3, 2024

Deploy Preview for apollo-client-docs ready!

Name Link
🔨 Latest commit 8fdbb5f
🔍 Latest deploy log https://app.netlify.com/sites/apollo-client-docs/deploys/66d76ac53cc4c40008d183e3
😎 Deploy Preview https://deploy-preview-12052--apollo-client-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link

netlify bot commented Sep 3, 2024

Deploy Preview for apollo-client-docs ready!

Name Link
🔨 Latest commit b4e5568
🔍 Latest deploy log https://app.netlify.com/sites/apollo-client-docs/deploys/66d886c0764b1300089d225d
😎 Deploy Preview https://deploy-preview-12052--apollo-client-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@jerelmiller jerelmiller force-pushed the jerel/fix-useFragment-warning branch from 2bc7646 to 74674ec Compare September 3, 2024 20:24
Comment on lines 78 to 88
const stableOptions = useDeepMemo(
// We default the `id` to a falsey string value to ensure `undefined` does
// not get passed to cache.identify in cache.watchFragment. If that happens,
// an obscure warning is displayed to the user
// (https://github.com/apollographql/apollo-client/pull/12052).
//
// `ROOT_QUERY` will be used as the default `id` in `cache.diff` if `id`
// is a falsey value.
() => ({ ...rest, from: id || "" }),
[rest, id]
);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have to admit, I really don't like the empty string workaround.
Given that watchFragment is still a very young api, could we maybe handle that over there, having it pass on an undefined value?

typeof from === "undefined" ? from : typeof from === "string" ? from : this.identify(from)

Copy link
Member Author

@jerelmiller jerelmiller Sep 4, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Welp, I should have just kept my original changes 🤣. I moved it in 74674ec for a couple reasons:

  • Our TypeScript types don't allow for undefined (technically) so this wasn't a supported use case. I believe you would have seen this already if you used cache.watchFragment directly and passed undefined to from (assuming you were using plain JS or ignored the TS errors)
  • We were using id! in useFragment which meant we were trying to circumvent what TS was already trying to warn us about (undefined not being supported) so it felt like the fix needed to be on the side of useFragment.

I'm fully willing to admit I'm overthinking this, but felt it a bit odd that our implementation was at odds with our supported types, hence this latest change.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see the reasoning - but, tbh., I'd rather add a little comment to the ! - the "special" handling of "" seems more like an accident to me and we might handle that differently at some point in the future, missing that we have to change this code path again.
That might be caused by something as trivial as replacing a || with a (logically much more fitting) ?? and trickle down in very weird ways.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds reasonable enough. Will revert the last commit and add an additional comment for the !

@jerelmiller jerelmiller force-pushed the jerel/fix-useFragment-warning branch from 74674ec to b4e5568 Compare September 4, 2024 16:11
Copy link
Member

@phryneas phryneas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me now!

@github-actions github-actions bot added the auto-cleanup 🤖 label Sep 4, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 6, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

UseFragment producing a warning during store misses (TypeError: Cannot read properties of undefined)
2 participants