Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Request for new functionality
View staffing
Description
We currently have cases where we change something inside of the
NavBackStackEntry, but keep the entry around (i.e. when changing arguments).This makes it difficult for the
NavControllerto detect there was a change, and in cases like compose where we rely on changes in theNavControllerto determine when to recompose, we have problems.We should instead make the
NavBackStackEntryimmutable and create a newNavBackStackEntrykeeping the sameLifecycleOwner,ViewModelOwner, etc, but with the new information that we actually do want to change.