Removing from composition and re-adding when navigating about compose-destinations HOT 3 CLOSED

Neither. It’s how Compose works in general. Not related with navigation official or this library.

The ViewModel is created as the corresponding screen becomes visible, so I would say you do have control over when it gets instantiated and you should also have control over when it happens on tests. This has never been an issue for me.
As a bonus, the UI shouldn’t be saying things like “load the list” to the VM. The VM is the one that decides what to do.
at most the UI can say “hey the UI is now visible” and then the VM makes the decision to load the list or not.

from compose-destinations.

Hi!

yes, this is expected. When you navigate forward, the back stack entry and the ViewModels are kept but the Composable leaves composition and re enters it when you navigate back. So the LaunchedEffect runs again.

for this use case, what I do usually is I load list on the constructor of the ViewModel. This is better in my opinion for multiple reasons.

from compose-destinations.

@raamcosta Thanks for the quick reply, sorry if it's a bad question, but is this feature of navigation or Compose Destinations?

The problem with loading something in constructor is that you have no control over it, eg in testing - your side effects are started by DI creating the instance, not you.

from compose-destinations.