Closed jerelmiller closed 2 months ago
Latest commit: a924c0f8e8955c792c08b8906c35493bde85b590
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.
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
Moving back to draft after discussion with @phryneas. Will put it back up for review after changes are made.
Closes https://github.com/apollographql/apollo-client/issues/11674 Closes https://github.com/apollographql/apollo-client/issues/11673
Adds support for an
@unmask
directive that disables data masking for a named fragment when data masking is enabled in the client.This directive will be most useful for migration when adopting data masking. As such, we've added the ability to emit warnings when using a
mode
argument set tomigrate
:When accessing
data.currentUser.name
, the user will see a warning in the console about accessing an unmasked field. Using@unmask
without themode
argument won't emit warnings.It is also possible to mix and match fragment subtrees with
@unmask
which allows a user to migrate a subtree at a time.