-
Notifications
You must be signed in to change notification settings - Fork 789
Error disappears on re-renders or after mutation #3406
Comments
I have a reproduction of @hwillson submitted PRs to fix this (#3339 and #3362), but the problem still occurs for me when I specify There was an existing issue about error disappearing on rerender, but it got closed when those PRs were merged: #3295. I was just about to submit a new issue about this, but I see you got to it first |
Update: I've found that the error only disappears on re-render if you are using an inline function for |
Also experiencing this using This started happening after we upgraded from |
I created a PR which I believe will fix this issue: #3419 |
@arianofaoms The fix for this issue hasn't been released yet |
Thanks for the reply. Any insights as to when it will be? |
@arianofaoms Should be available now. v3.1.0 just released |
@dylanwulf @arianofaoms I confirm that 3.1.0 fixes the problem in my project. |
@dylanwulf @hwillson @arianofaoms This behaves flaky in 3.1.3. |
Intended outcome:
When
error
andloading
are NOT truthy, data should existActual outcome:
How to reproduce the issue:
To be honest, I cannot reproduce it using https://github.com/apollographql/react-apollo-error-template
In my application everything works fine until:
loading, error, data
is corrupted like:This problem also appears on
3.0.1
.I will try and create reproducible repo but it's quite challenging.
I suppose that it's related with cache configuration because it looks like:
id
field which is taken from variables passed to that queryVersion
The text was updated successfully, but these errors were encountered: