Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
fix(routing): fix history router based on history length #5004
fix(routing): fix history router based on history length #5004
Changes from 7 commits
fc1cb8e
17938f9
f839220
8cdda05
4ddd41f
d945d32
2192463
402d9e0
e716db2
72b5b88
e670f2c
de02dca
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
question (non-blocking): to be fully clear, this is the behavior we want to document (third-party router did initiate a navigation but wrote later, so we can't "escape" an in-between write), correct?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In our testing, this behaviour doesn't actually happen, as route navigations happen immediately, no debounce.
We are testing it to be aware if it ever changes, but that doesn't mean we think this is 100% correct behaviour (ideally the in-between update doesn't happen either.
How could that be made more clear in the test?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The scenario as I understand it is:
/?indexName[query]=Apple
)/
)/about
)If yes I think this is clear, but we should probably document it because having this intermediary
/
route can be surprising.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
question: Why is this commented? It does affect the test output.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should be removed indeed, here we do not want to wait until the url is written
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup we do it in the next step.
Is this a behavior worth documenting? Should we say that our router doesn't work well with other routers that use
replaceState
?