-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Apollo2.0 - FragmentMatcher not enabled/picked up #2246
Comments
So I managed to fix the fact that the fragmentMatcher was not being picked up. I fixed it by reverting to the old way of installing the fragmentMatcher i.e. placing the property directly in the client's parameter object like so:
as opposed to placing it on the InMemoryCache config parameter like so:
Either the 2.0 upgrade doc needs to change or the library needs to be fixed. |
hmm that doesn't seem right. Do you have a reproduction I can look at to verify whats happening? |
Fixed with #2281 It should be on the |
@serle try |
@jbaxleyiii thx will do |
Thanks: confirming @jbaxleyiii findings & the fix for this issue. |
Upgraded to beta.5 but it is still not working. This is my initialization code (where I get fragment matcher errors)
This works:
but fragmentMatcher is in the wrong place according to docs |
@serle Did you find a solution for this problem? |
@dbelchev I'm still using the second method in my comment above |
I have several union types in my schema and have added the IntrospectionFragmentMatcher to the InMemoryCache as specified in the docs. I don't think the fragmentMatcher is being used as I am getting these warnings. I'm using "apollo-cache-inmemory": "^0.1.0-0", however when I upgrade the the beta version I get a store update error.
The rest of my apollo stack is:
"apollo-client": "^1.9.3",
"apollo-link": "^0.7.0",
"apollo-link-http": "^0.7.0",
The text was updated successfully, but these errors were encountered: