feat(memory-location): add state support#557
Open
wotan-allfather wants to merge 1 commit intomolefrog:v3from
Open
feat(memory-location): add state support#557wotan-allfather wants to merge 1 commit intomolefrog:v3from
wotan-allfather wants to merge 1 commit intomolefrog:v3from
Conversation
This PR adds state support to memoryLocation, similar to how useBrowserLocation handles history.state. This allows passing down state in testing scenarios and in-memory routing. Changes: - Add optional `state` parameter to memoryLocation options for initial state - Accept `state` option in navigate function to update current state - Add `state` getter property to access current state value - Add `stateHook` for subscribing to state changes in components - Reset state to initial value when `reset()` is called The implementation follows the pattern suggested in issue molefrog#492 by @molefrog. Closes molefrog#492
|
|
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
1 participant
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.
This PR adds state support to memoryLocation, similar to how useBrowserLocation handles history.state. This allows passing down state in testing scenarios and in-memory routing.
Changes:
stateparameter to memoryLocation options for initial statestateoption in navigate function to update current statestategetter property to access current state valuestateHookfor subscribing to state changes in componentsreset()is calledThe implementation follows the pattern suggested in issue #492 by @molefrog.
Closes #492