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