apollo-client-preset 1.0.7 breaks @client directive in apollo-link-state
See original GitHub issueIntended outcome:
Upgrading apollo-client-preset
from 1.0.6
to1.0.7
should not break custom directive @client
in apollo-link-state.
Actual outcome:
@client
directive in apollo-link-state
no longer works. The might be due to recent addition of custom directive feature in apollo-cache-inmemory@1.1.6
How to reproduce the issue:
-
Install
apollo-link-state@^0.3.1
along withapollo-client-preset@^1.0.6
and implement local client query using@client
directive. -
Upgrade to
apollo-client-preset@^1.0.7
–@client
directives no longer works.
Issue Analytics
- State:
- Created 6 years ago
- Comments:16 (2 by maintainers)
Top Results From Across the Web
Local state management - Apollo GraphQL Docs
You'll notice in our query that we have a @client directive next to our visibilityFilter field. This tells Apollo Client to fetch the...
Read more >Mixing client and server state in query leads to error · Issue #140
Let's say I have a query like this: query StoryLayout($storyId: ID!) { tutorial @client story(id: $storyId) { id } } This throws with...
Read more >apollo-client-preset | Yarn - Package Manager
Use create-react-app then yarn add apollo-client-preset react-apollo graphql and replace below code for index.js import * as React from 'react' import ...
Read more >Intro to Apollo Client 3.0 - YouTube
On this episode of Mission Briefing, Ben Newman (@benjamn) walks Kurt Kemple (@kurtkemple) through Apollo Client 3.0! Apollo Client 3.0 ...
Read more >Using Apollo Client with a REST API | by November Five
});. Later on we will use this endpoint to illustrate how data fetching with apollo-link-rest works in React. QUERIES. We ...
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
Thanks for reporting this! Hoping to get a fix out as soon as possible 😃
Well done @barbalex ! I also thought it was apollo-utilities, but I’m not experienced enough with flushing NPM caches to get clean installs… I kept chasing my tail and wasn’t able to reproduce the fix reliably.
I rolled back apollo-client to 2.0.4, apollo-cache-inmemory to 1.1.0 and apollo-utilities 1.0.3, and after yelling and screaming enough, finally a node_module clear and npm install worked