This repository has been archived by the owner on Oct 1, 2024. It is now read-only.
Allow passing a fetchPolicy to useBackgroundQuery
#1293
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tleunen
force-pushed
the
useBackgroundQuery
branch
from
559d5ae to
66be26b
Compare
lemonmade
approved these changes
Feb 23, 2020
tleunen
force-pushed
the
useBackgroundQuery
branch
from
66be26b to
29df293
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
useBackgroundQuerydoesn't currently allow passing a customfetchPolicy, but it will still forward the options toclient.watchQuery().So I've decided to allow it as it might be useful for some people (like me) which would like to trigger a cache-first query instead of the default network-only query.
Type of change
react-graphqlPatch: Bug/ Documentation fix (non-breaking change which fixes an issue or adds documentation)Checklist