Skip to content

chore: refactor router client history update #1515

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

Draft
wants to merge 8 commits into
base: main
Choose a base branch
from

Conversation

rmarscher
Copy link
Collaborator

@rmarscher rmarscher commented Jul 9, 2025

Follow up to #1459

Copy link

vercel bot commented Jul 9, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Project Deployment Preview Updated (UTC)
waku Ready Preview Aug 13, 2025 3:54am

Copy link

codesandbox-ci bot commented Jul 9, 2025

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Copy link

pkg-pr-new bot commented Jul 9, 2025

Open in StackBlitz

npm i https://pkg.pr.new/wakujs/waku@1515

commit: c6ee137

@rmarscher
Copy link
Collaborator Author

It looks like there are still failing tests. Changing to draft while I fix.

@rmarscher
Copy link
Collaborator Author

I'm just learning about the transition inside a transition pattern. That is probably why the startTransitionFn is also called after await changeRoute. I should probably revert the changes to unstable_startTransition in this PR and reconsider.
https://react.dev/reference/react/useTransition#react-doesnt-treat-my-state-update-after-await-as-a-transition

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant