-
Notifications
You must be signed in to change notification settings - Fork 986
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
fix navigation reset #9208
fix navigation reset #9208
Conversation
Pull Request Checklist
|
Jenkins Builds
|
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.
Thanks @yenda! This means that in all places we use navigate-reset currently, we have to modify the params map passed so as not to have issues with navigate-back, is that the case?
@siphiuel no it just means that now you can have more than one item in the actions vector, previously you could basically only reset to one of the top routes, there is an example in my ens PR |
@churik is this e2e test suppose to pass? |
@yenda for next times: look at Failure screenshot in test_decline_invitation_to_group_chat. |
currently navigation-reset only works properly if you reset to a simple route this fix allows us to use navigation reset with more complex routes, by ensuring that the navigation stack is populated properly so that navigate back doesn't end up emptying the stack. this is temporary as the proper way to do navigation in general would be to get rid of view id and navigation-stack entirely, since it is a duplication of the state of react-navigation Signed-off-by: yenda <[email protected]>
e17ac85
to
500d2cc
Compare
currently navigation-reset only works properly if you reset to a simple route
this fix allows us to use navigation reset with more complex routes, by
ensuring that the navigation stack is populated properly so that navigate
back doesn't end up emptying the stack.
this is temporary as the proper way to do navigation in general would be
to get rid of view id and navigation-stack entirely, since it is a duplication
of the state of react-navigation
status: ready