Skip to content
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

When using the useQuery hook errors get cached. #177

Closed
jcblw opened this issue Aug 3, 2021 · 1 comment · Fixed by #204
Closed

When using the useQuery hook errors get cached. #177

jcblw opened this issue Aug 3, 2021 · 1 comment · Fixed by #204
Labels
core issue or PR for the core of finch-graphql package. help wanted Extra attention is needed

Comments

@jcblw
Copy link
Contributor

jcblw commented Aug 3, 2021

Seems like our cache is pretty sticky in the hook, and will not clear out an error, once its resolved. We ran into an error with this when trying to get Firefox working and dealing with the external messaging script. Essentially we would poll and get errors because the script was not ready. Once the script was ready we got back data but the error persisted.

@jcblw jcblw added help wanted Extra attention is needed core issue or PR for the core of finch-graphql package. labels Aug 3, 2021
@jcblw
Copy link
Contributor Author

jcblw commented Sep 6, 2021

Seems like this is sorta an issue with queries as well. I have seen where the old data is shown after a loading state for a split second.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core issue or PR for the core of finch-graphql package. help wanted Extra attention is needed
Development

Successfully merging a pull request may close this issue.

1 participant