feat(ReactQueryConfigProvider): update defaultConfigRef#775
Merged
tannerlinsley merged 1 commit intoTanStack:masterfrom Jul 22, 2020
Merged
Conversation
`useConfigContext` will always be populated. Checking the context value before defaultConfig update
|
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/tannerlinsley/react-query/8ct7sxqqb |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
useConfigContextwill always be populated. Checking the context value before defaultConfig update.I was assuming that this was the original intent of the code and this change fixes an issue I was experiencing where
queryCache.prefetchQuerywas not seeing the defaultqueryFnset in the provider.