···8787## Tracking unused fields
88888989Currently the tracking unused fields feature has a few caveats with regards to tracking, first and foremost
9090-it will only track in the same file to encourage [fragment co-location](https://www.apollographql.com/docs/react/data/fragments/#colocating-fragments).
9191-Secondly it supports a few patterns which we'll add to as time progresses:
9292-9393-```ts
9494-// Supported cases:
9595-const result = (await client.query()) || useFragment();
9696-const [result] = useQuery(); // --> urql
9797-const { data } = useQuery(); // --> Apollo
9898-const { field } = useFragment();
9999-const [{ data }] = useQuery();
100100-const {
101101- data: { pokemon },
102102-} = useQuery();
103103-```
9090+it will only track the result and the accessed properties in the same file to encourage
9191+[fragment co-location](https://www.apollographql.com/docs/react/data/fragments/#colocating-fragments).
10492105105-Lastly we don't track mutations/subscriptions as some folks will add additional fields to properly support
9393+Secondly, we don't track mutations/subscriptions as some folks will add additional fields to properly support
10694normalised cache updates.
1079510896## Fragment masking