Local only fields don't work with subscriptions

Evgheni_Anachii · October 26, 2023, 2:24pm

I followed the steps from Local-only fields in Apollo Client - Apollo GraphQL Docs and in case I use apollo query I get that local field in my graphQl response, however, if I do an apollo subscription there is no such field in the response. Why for subscriptions, fields marked as @client are not even presented in the response? Neither read function (I set into InMemoryCache) is not executed.

JeffAuriemma · October 31, 2023, 2:58am

Hi @Evgheni_Anachii - this is a known issue that we are tracking. We don’t have a fix yet but please feel free to follow this issue for updates:

github.com/apollographql/apollo-client

Return local-only fields in subscription responses

opened 06:17PM - 21 Sep 23 UTC

Narretz

🔍 investigate

Right now, if you use `@client ` in gql subscription response, the field is neve…r populated. This is probably because subscription responses aren't cached like queries, even though individual types are cached. However, this is extremely counter intuitive. A subscription response isn't that different from a query response. InMemoryCache should populate the local only fields once after the data is received. Otherwise it should be clearly stated in the docs that this is not possible, or apollo client should throw if a subscription gql document contains the `@client` directive.

Topic		Replies	Views
Issue with local-only fields Help client , web	3	866	July 15, 2021
cache.readQuery - local field and new schema version Help client , web	1	368	June 23, 2022
@apollo/client local-only field is not resolved when working with service worker Help client	5	731	December 4, 2023
Local sotrage for GraphQl Help client , web	0	322	May 10, 2022
Is there an easy way to switch between remote schema-based queries and queries that use similar local-only fields? Help	2	316	January 11, 2024

Local only fields don't work with subscriptions

Related topics