Repository navigation
fix(core): Frame navigatingToEvent event fix - #9954
Merged
Merged
Conversation
the event has no real use if we dont get access to `resolvedPage`
NathanWalker
force-pushed
the
farfromrefug-patch-1
branch
from
July 9, 2022 16:05
f82e418 to
ff9d35b
Compare
NathanWalker
pushed a commit
that referenced
this pull request
Jul 9, 2022
BREAKING CHANGE: When using `navigatingToEvent` event.entry, the `backstackEntry` object is now returned which has an `entry` property on it if you still need it.
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.
the event has no real use if we dont get access to
resolvedPagePR Checklist
What is the current behavior?
What is the new behavior?
Fixes/Implements/Closes #[Issue Number].