Skip to content
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

[Bug]: Active fetcher is not revalidated when explicit fetcher key is used #12067

Open
gforro opened this issue Oct 4, 2024 · 0 comments
Open
Labels

Comments

@gforro
Copy link

gforro commented Oct 4, 2024

What version of React Router are you using?

6.26.2

Steps to Reproduce

I have already reported the bug in remix-run/remix repo, which rather belongs to this repository: remix-run/remix#10053
I have reported it in the remix repository as I have observed the problem in the Remix framework.

Expected Behavior

Active fetcher is revalidated after form submission or when the revalidator.revalidate() is called.

Actual Behavior

Fetcher in a mounted component is not revalidated after form submission or when the revalidator.revalidate is called. This happens only if future.v7_fetcherPersist = false mode is used.
The problem can appear only if there are multiple fetchers with the same fetcher key rendered in the very same page (see linked remix-run/remix bug for further detail)

@gforro gforro added the bug label Oct 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant