-
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
query() returns null-data #3519
Comments
I found out that the complete-field of the newData-field of the query is set to false. The only place where this is set seems to be in the fetchRequest()-function:
Thus, this is only set for fetch policy "no-cache". The code that evaluates the complete-field is Any idea? |
Any chance you could put together a small runnable reproduction for this? That would greatly help with troubleshooting. Thanks! |
I'm sorry, I didn't close this issue...it was a problem on my machine: for some reason graphql-tools wasn't updated and caused big trouble. |
I believe you might had encountered the problem I described here: #3030 (comment) |
Hallo,
I've got an Angular app and today updated from Angular Client 2.2.2 to the latest version 2.3.1. Suddenly, queries don't work anymore. For example, the following small code snippet always results in:
Here is the snippet:
Is this a known issue? I debugged into Apollo Client and I could see that the real data was actually received in QueryManager.fetchRequest, but from that point on the code is rather complicated for a starter like me.
Further info: with fetch policy "no-cache" the data is correctly returned.
The text was updated successfully, but these errors were encountered: