Issue with using ResultRecipient across modules with dependancy about compose-destinations HOT 3 OPEN

Ksp task runs in each module separately and so it doesn’t know about classes in other modules.

This is for now expected and you do have to use the Open approach. I would like to know why does it make things very complicated, can you give me more info about that?

When manually calling your screen, you should be in a position where you can easily prepare the same dependencies you were in dependencyContainerBuilder, right?

I’ll keep this open though maybe I have an idea about how I could improve this for v2.

from compose-destinations.

Ok so the recepient screen looks like this

fun RecepientScreen(
    viewModel: RecepientViewModel,
    resultRecipient: OpenResultRecipient<CustomType>
) {
}

that view model gets injected through your library using dependenciesContainerBuilder. We do this because we are sharing that VM between 2 screens and we want it to stay alive and shared between those 2 screens.

in the Destinations nav host if I try to manual create the screen then I have to manually pass in the view model and I'm not sure how to do that while maintaining that shared view model functionality

DestinationsNavHost(
 dependenciesContainerBuilder = {  CreateRecepientScreenVM()   }
) {
                    composable(RecepientScreenDestination) {
                        RecepientScreen(
                            viewModel =  / what goes here? /,
                            resultRecipient  = resultRecipient<ResultProducerScreenDestination, ResultType>())
                    }
                }

CreateRecepientScreenVM() is an extension function we created to create the viewModel but it only can be called in the context of dependenciesContainerBuilder

from compose-destinations.

Sorry for delay in response here 🙏

There is no reason why CreateRecepientScreenVM() should be able to be called in one place but not the other. Both have similar receivers in the lambda (Some kind of DestinationScope).
Try having the CreateRecepientScreenVM be an extension function of DestinationScopeWithNoDependencies. Then you should be able to call it on both manual calls and dependency builders cases 🙂

Hope this helps!

from compose-destinations.