apollographql / apollographql/apollo-client-integrations

RFC data masking - warning "no-cache"

Open
#486 9 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
TypeScript
Stars
556
Forks
53
PR merge metrics
No merged PRs in 30d

Description

Hi there.

I’m using the library with data masking enabled, and while everything seems to work functionally, I keep getting the following warning in the console:

```
[SERVER]: Fragments masked by data masking are inaccessible when using fetch policy "no-cache". Please add `@unmask` to each fragment spread to access the data.
at:

```

Here’s what I’ve tried:
• I added a fetchPolicy="cache-first" directly to the component.
• I also verified that my fragments include all necessary fields and are used as expected.
• However, the warning still shows up regardless of the fetch policy setting.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the warning with data masking, , fragments, and the reported fetch-policy settings. Compare the effective policy at the server call with the component setting; done means the warning's cause and the required fix are established, with behavior verified against the reproduction.

Written by the indexing model from the issue text.

Assessment

Tech stack
graphql, next.js, typescript
Domain
api, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.