feat(memory-location): add initial location state support#564
Merged
molefrog merged 1 commit intoMay 17, 2026
Conversation
|
|
molefrog
reviewed
May 17, 2026
d0fc622 to
86c3019
Compare
Owner
|
Thanks, planning this for the next release |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Adds initial state support to memoryLocation, so tests and custom in-memory routing setups can seed the current location state and read it back from the returned object.
This change keeps the API small:
The value is intentionally exposed on the memoryLocation(...) result object rather than as a destructured snapshot, so it always reflects the latest navigation state.
Changes
memoryLocationreset()restore the initial state as well as the initial pathwouterandwouter-preactTesting
Closes #492