-
Notifications
You must be signed in to change notification settings - Fork 5
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
chore: dismiss all before returning home #227
Conversation
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.
utACK
if (router.canDismiss()) { | ||
router.dismissAll(); | ||
} | ||
router.navigate("/"); |
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.
is this navigation even needed if we dismiss all the routes? shouldn't this be the default?
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.
Won't this also push a route onto the stack, leaving a back button?
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.
Navigate actually goes to "/" if available (which is actually the only screen in the stack after dismissAll
), so it doesn't add a back button
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.
is this navigation even needed if we dismiss all the routes? shouldn't this be the default?
Makes sense, removed navigation
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.
EDIT: please check comments
Addressed, should be good now! |
This removes the back button in the header, if you cancel/finish setup
Note: for some reason, this cannot be observed in Expo Go but the production build also has this issue.
Screenshots