Fixes new pageData not being used in old StandardPage's brought back to the top of the navigation stack. #30
Conversation
This file contains 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
…lable to non-nullable and null data is trying to be restored on route load. fix: fix an issue where if you navigate to an existing StandardPage, the old pageData would not be overridden with the new pageData.
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.
fix: Fix an issue when StandardPage page data's type changes from nullable to non-nullable and null data is trying to be restored on route load.
fix: fix an issue where if you navigate to an existing StandardPage, the old pageData would not be overridden with the new pageData.
Issue Number
fixes #28
fixes #29