Thanks @lenz that you care about my issue.
Yes, this far it is expected, that the field is left from the API request. It just doesn’t happen, that the typePolicy for my field is considered.
This is one of the responses I have:
{
"token": {
"id": "908fd53a-cb88-432b-8c2d-1fbcec500a8a",
"address": "578b9a18-7b07-4028-8354-7861f78b22ea",
"symbol": "CUP",
"createdAt": "2023-09-07T16:13:40.183Z",
"priceUSD24hAgo": 2467.94,
"isPoolToken": false
},
"walletAmount": null,
"troveMintedAmount": null,
"stabilityLostAmount": null,
"stabilityCompoundAmount": null,
"totalDepositedStability": 4310.92,
"totalReserve": 0,
"totalReserve24hAgo": 0,
"totalSupplyUSD": 11552.7,
"totalSupplyUSD24hAgo": 16380.9,
"stabilityDepositAPY": 0.1
}
This is not the response from the mock service worker but my logged value from useQuery
. This is the symptom of the same issue that I “dont see the console.log from my typePolicy”. The typePolicy for “priceUSD” is not used to resolve the @client field somehow.
I have tried to follow the guide on local-only fields to the best of my abilities.