Skip to content

fix: fetcher submission revalidating fetchers using wrong key #9166

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

Merged
merged 2 commits into from
Aug 18, 2022

Conversation

brophdawg11
Copy link
Contributor

Fixes a bug where revalidating fetchers triggered by a separate submitting fetcher would temporarily have their data messed up, and due to the wrong key usage it would reflect the submitting fetcher action data.

@changeset-bot
Copy link

changeset-bot bot commented Aug 18, 2022

🦋 Changeset detected

Latest commit: b88bcfd

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 5 packages
Name Type
@remix-run/router Patch
react-router Patch
react-router-dom Patch
react-router-dom-v5-compat Patch
react-router-native Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@brophdawg11 brophdawg11 merged commit 1dc082c into dev Aug 18, 2022
@brophdawg11 brophdawg11 deleted the brophdawg11/fix-fetcher-revalidation branch August 18, 2022 13:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant