vovahost / navigationmvvm Goto Github PK

Hi Vladimir Ostaci. I gave this a try in my app. I have a fragment that I reuse like a nested menu, and I share a ViewModel between these instances to track where the user is. For details: https://stackoverflow.com/questions/71025002/how-can-i-correctly-implement-custom-back-navigation-in-a-re-used-nestable-frag

Unfortunately I wasn't able to get it to work. However, a suitable workaround can be found here: https://developer.android.com/guide/navigation/navigation-programmatic#returning_a_result

In the lambda, _ // Do something with the result._ I was able to call ViewModel.onBackPressed(). It's a bit tightly coupled from the View to the Viewmodel, but for now, it solves my problem of too many onBackPressed callbacks getting assigned, and works as I intended it to. Just letting you know in case it might be relevant to your article here https://engineering.nodesagency.com/categories/android/2019/08/15/android-navigation-tools