You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/source/data/fragments.mdx
+2-3Lines changed: 2 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1561,12 +1561,11 @@ You can use a technique called 'higher-kinded types' (HKT) to provide your own t
1561
1561
1562
1562
Let's add our own type overrides for the `MaybeMasked` and `Unmasked` utility types.
1563
1563
1564
-
The `MaybeMasked` type is used throughout Apollo Client to return the masked or unmasked type definition for a given type, assuming they have data masking types enabled and are "mask-able" - otherwise it will just return the "unmasked" type that is passed in.
1565
-
(So when writing these types, you can assume that the user has data masking types enabled.)
1564
+
The `MaybeMasked` type is used throughout Apollo Client to return the masked or unmasked type definition for a given type, assuming they have data masking types enabled and are "mask-able" - otherwise it will just return the "unmasked" type that is passed in.
1566
1565
1567
1566
The `Unmasked` type unwraps a masked type to its full result type and is used throughout Apollo Client where the full data type is needed for a given API (e.g. `client.writeQuery`).
1568
1567
1569
-
For this example, we'll assume the operation types are generated using two variations:
1568
+
For this example, we'll assume the data masking types are enabled and the operation types are generated using two variations:
1570
1569
1571
1570
1. Data masked types are generated with a `__masked` virtual property. Its value is the operation type with any masked fields removed from the type.
0 commit comments