fix(clerk-js): Add optional resourceId to useFetch hook
#5536
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.
Currently,
useFetchcaches data using only a string-ified version of the params as a key, which very easily leads to cache collisions.This adds an optional
resourceIdparam that is used in conjunction with the params to create the cache key. This is optional and not breaking.Checklist
pnpm testruns as expected.pnpm buildruns as expected.Type of change