-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
redirect in child action doesn't refresh parent loader #8783
Comments
What does the Network tab look like? |
Here's a video. Notice how only after a manual refresh does the left bar reload the data. Area.mp4 |
This actually seems to be a problem with react arborist. Closing this issue since it's not remix related. |
Just thought I'd add a comment on here in case anyone searches. I was having a similar problem where it seemed my action wasn't reloading the parent loader. Turns out my page had a cancel button (which was a link) on it with a prefetch set to intent. I also set some cache headers on prefetch.
So, I happened to be hovering the cancel button before I got to the submit button. This was sending a prefetch that was cached by the time I hit the submit button and redirected. I was able to figure that out by looking at the network tab and seeing that the parent loader was actually being served by a prefetch cache. Removing the intent fixed the problem. footgun :) |
Reproduction
I have an action in some leaf route
app/routes/team.$team.$workspace.$query.$index.tsx
And the action is being submitted via a useFetcher
And the child route correctly reloads all data, but the parent route's loader in app/routes/team.$team.tsx doesn't.
Is this expected? It feels like all loaders should be reloaded on mutation events.
System Info
Used Package Manager
npm
Expected Behavior
All loaders to refresh
Actual Behavior
only child loaders are refreshed
The text was updated successfully, but these errors were encountered: