Skip to content

docs: fix parentTypename casing in graphcache local resolvers - #3900

Open
latent-9 wants to merge 1 commit into
urql-graphql:mainfrom
latent-9:docs/fix-parenttypename-casing
Open

docs: fix parentTypename casing in graphcache local resolvers#3900
latent-9 wants to merge 1 commit into
urql-graphql:mainfrom
latent-9:docs/fix-parenttypename-casing

Conversation

@latent-9

@latent-9 latent-9 commented Aug 1, 2026

Copy link
Copy Markdown

The local resolvers guide reads the parent typename from info as info.parentTypename:

Read the current parent entity's typename using info.parentTypename

The actual ResolveInfo field is parentTypeName (capital N) — see exchanges/graphcache/src/types.ts, and it's already spelled correctly in the API reference (docs/api/graphcache.md). The lowercase info.parentTypename doesn't exist, so copying this example returns undefined. Corrected the casing.

The local-resolvers guide references `info.parentTypename`, but the ResolveInfo
field is `parentTypeName` (exchanges/graphcache/src/types.ts) — as already spelled
correctly in the API reference (docs/api/graphcache.md). Corrected the casing.
@changeset-bot

changeset-bot Bot commented Aug 1, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 83f1d97

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant