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
Navigation.isActiveRoute function updated to handle currentRoute logic #4382
Navigation.isActiveRoute function updated to handle currentRoute logic #4382
Changes from 1 commit
7fb86db
b7658db
f26b5a0
e43b311
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.
Apart from https://reactjs.org/docs/hooks-rules.html#only-call-hooks-from-react-functions. All good.
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.
Okay. But it seems that using
getPathFromState
will have to also be inside a component only. Any suggestions on this?React Navigation suggests this approach:
https://reactnavigation.org/docs/screen-tracking/#example
The second approach would then be creating a ref in
Navigation
export const currentRouteRef = React.createRef();
and in NavigationRoot.parseAndStoreRoute
currentRouteRef.current = path;
and this quite similar to fetch URL from Onyx
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.
It is already using navigationRef in the isActiveRoute. but NAB.
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.
We should have kept using
getCurrentRoute().path
as the first resource and only fallback tobuildLink
if needed. This is because theuseLinkBuilder
orgetPathFromState
does not work well with urls that contain encoded parameters.react-navigation
encodes every param even the encoded ones resulting in double-encoded urls. Those double-encoded urls won't match with the user's urls. - Coming from #33001