feat: support functional swr context config #2024
Merged
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.
Background
SWRConfig
now merges the config passed invalue
property with SWR config from parent context, but this bring a problem that users have to be aware of how many layers of context are existing and there's no way to ignore the config from parent contextFeature
(parentConfig? Config) => Config
overloading forSWRConfig
value propertyThen you can pick any properties from parent config and decide how to combine with the current SWR config, or you can just ignore any config property from parent context. e.g. you have a
useSWR
hook inside very deep level of the react tree, but you want it to keep the default config, you can just ignore all configs by ignoring all the parent configs.Example