This PR proposes changing the default behavior of Nuvigator to not rebuild/reload from scratch when the NuRouter instance changes, which is especially relevant for nested flow. This is motivated by the following points:
Development experience is compromised with the current behavior, that without proper state management, at every hot-reload the flow is reset
Some use cases of nested flows were suffering from resets when the upper state of the tree changed
While we expect this to be a fix/improvement for most cases, it's feasible to this being used as a feature for current users. Due to that, this can be considered a breaking change, and in those cases, you can provide a shouldRebuild function to the Nuvigator specifying the desired conditions to meet your previous behavior.
This PR proposes changing the default behavior of Nuvigator to not rebuild/reload from scratch when the NuRouter instance changes, which is especially relevant for nested flow. This is motivated by the following points:
While we expect this to be a fix/improvement for most cases, it's feasible to this being used as a feature for current users. Due to that, this can be considered a breaking change, and in those cases, you can provide a
shouldRebuildfunction to theNuvigatorspecifying the desired conditions to meet your previous behavior.