-
Notifications
You must be signed in to change notification settings - Fork 4
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
ensurePrimary doesn't work fine #6
Labels
Comments
Can you make a reproduction? |
Well, it's not that easy to reproduce, because it doesn't happen to all users. |
I'm afraid I don't have bandwidth to investigate this. But I'd be happy to look at a pull request if you work out what's going wrong. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I had a route which I put await
ensurePrimary()
on the loader because I was doing a update() request with prisma, and includingawait ensurePrimary()
on the loader, was making all the links to that loader (both with useNavigate and remix Link) to reload the current page instead of go to that new page.So I ended removing
ensurePrimary()
, and the links worked again.The text was updated successfully, but these errors were encountered: