-
Notifications
You must be signed in to change notification settings - Fork 13.5k
fix(react): Nav unmounts component while invoking popTo or popToRoot #27821
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
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.
Thank you for this contribution!
I ended up checking out your branch and pushing some changes to avoid an API change to the ReactDelegate
. We can create a unique id for each delegate constructed and increment a counter for each view pushed onto the stack.
I've also updated the test app to check that the page unmounted lifecycle is called when popping to the root of the stack.
Once we have another +1 from the team, this is good to go 🎉
Thank you! |
…27821) Issue number: Resolves #27798 --------- ## What is the current behavior React IonNav component's views are missing keys, leading to unnecessary duplicate mounting of components. ## What is the new behavior? - Adds key to views of React IonNav component. ## Does this introduce a breaking change? - [ ] Yes - [x] No --------- Co-authored-by: Sean Perkins <[email protected]>
…27821) Issue number: Resolves #27798 --------- ## What is the current behavior React IonNav component's views are missing keys, leading to unnecessary duplicate mounting of components. ## What is the new behavior? - Adds key to views of React IonNav component. ## Does this introduce a breaking change? - [ ] Yes - [x] No --------- Co-authored-by: Sean Perkins <[email protected]>
Issue number: Resolves #27798
What is the current behavior
React IonNav component's views are missing keys, leading to unnecessary duplicate mounting of components.
What is the new behavior?
Does this introduce a breaking change?