Apollo Link State queries not supported
See original GitHub issueApollo Link State (client state handling for Apollo) uses the @client
directive for queries that query the local state. They can look like this:
query {
amount @client {
amount
}
}
These seem to not be supported in the plugin, see attached:
Issue Analytics
- State:
- Created 6 years ago
- Reactions:6
- Comments:8
Top Results From Across the Web
Persisted Queries Link - Apollo GraphQL Docs
GET requests are not compatible with @apollo/client/link/batch-http . If you want to use GET for non-mutation queries whether or not they are hashed, ......
Read more >Custom query resolvers not working · Issue #196 - GitHub
I think, for local state query, request method at this line is not getting invoked. Data is returned from cache before hitting request....
Read more >Apollo Link State Default Resolver Not Working (@client query ...
The default resolver for todos returns all the todos in the defaults, as expected. The default resolvers don't do anything with arguments passed ......
Read more >Local State Management – Angular - GraphQL Code Generator
As of Apollo Client 2.5, local state handling is baked into the core, which means it is no longer necessary to use apollo-link-state...
Read more >Migrating to Apollo Client 3.0
It is important to note that Apollo Client 3 no longer allows @client fields to be passed through a Link chain. While Apollo...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Schema directives fixed in https://github.com/jimkyndemeyer/js-graphql-intellij-plugin/releases/tag/2.0.0-alpha-3
If you add the following into your GraphQL schema, it should prevent this from showing as an error.