feature: Provide a way to detect when navigation to a view-model is completed, even if no navigation-parameter is being passed

[AlexanderMelchers]

feature: Provide a way to detect when navigation to a view-model is completed, even if no navigation-parameter is being passed

[winterdouglas]

I'd say this could be potentially closed and you could keep an eye on the #197 :)
@RLittlesII

[open-collective-bot]

Hey @AlexanderMelchers 👋,

Thank you for opening an issue. We will get back to you as soon as we can. Also, check out our Open Collective and consider contributing financially.

https://opencollective.com/reactiveui

PS.: We offer priority support for all financial contributors. Don't forget to add priority label once you start contributing 😄

ReactiveUI - Open Collective

An advanced, composable, functional reactive model-view-viewmodel framework for all .NET platforms!

[winterdouglas]

Hey @AlexanderMelchers , I was looking the code here and actually what you are requesting can be done already in some way. The WhenNavigatingTo and WhenNavigatedTo are called every time a push happens, the only pre-requisite to have that working is to be using the ParameterViewStackService and call the Push passing in yourself an empty dictionary as a parameter. If you instead call the Push methods without the parameter signature (from the ViewStackService) then indeed those won't be triggered, so I guess that's your case.

Ideally I'd say we should have some kind of special "hook" to have that in a more consise way, there's a feature request I opened for that here #197

[RLittlesII]

@AlexanderMelchers Apologies for not commenting on this sooner. What @winterdouglas says is accurate, the methods get called every navigation and there is nothing preventing you from hooking into them with an empty dictionary. Some base ViewModel class that handles it will get you that information.

We are looking into ways to provide better life cycle methods for the ViewModel. I feel like this is basically the same thing you are requesting. I am going to close this issue as it is similar to the other feature request and solving one, should solve both.