local state not working

I followed the tutorial at https://www.apollographql.com/docs/tutorial/local-state/ Whenever I include the local state as in export const LAUNCH_TILE_DATA = gql' fragment LaunchTile on Launch { id isInCart @client isBooked rocket { id name } mission { name missionPatch } } '; then the Query only returns {} . If I remove isInCart @client, then the query is successful and gives the launch information. What’s wrong with the local state?

[lifeiscontent]

@hwillson Thanks for asking. with-apollo requires you to have a root query for each individual page. getDataFromTree allows you to not have to expose a root query. There are also issues with the ergonomics of next.js e.g. if you have a query that depends on query parameters, the react context for the next.js router I don’t believe is populated so using getDataFromTree is pointless in that case.

Also, it would be nice to see how to handle the case that I mentioned, e.g. theirs an error via SSR in graphql but then cleared out due to the data of the query being cleared out because the Apollo cache doesn’t store errors in it. But in production environments it’s very important to not drop errors. There is currently not a defined practice on how to handle these kinds of cases. Feel free to message me directly if you want more details. Happy to chat!

[lifeiscontent]

Based on my experience with Next.js and Apollo Client, Both technologies are good, but they’re not good together due to how they are expected to be used. But maybe I just don’t understand something and if possible, it would be great to have some of this confusion uncovered.