resultRecipient() support for Destinations from other modules when one depends on the other module

Would be awesome if resultRecipient() supported Destinations from other modules when the recipient module depends on the sender.

In the current state, this error is thrown.

Non existent Destination as the ResultRecipient's result origin!

[raamcosta]

Wasn’t able to allow this without losing some type safety at compile time + some manual work when calling DestinationsNavhost. So the fix is not ideal for this particular scenario where the recipient module actually depends on the sender module.

Since I need to have information about the Destination to check if it also contains a correspondently typed result, I didn’t find a better solution. I think I will reopen this however, so I can maybe explore more in the future 😃

In the meantime, I wanted to make this possible even when modules don’t depend on eachother, so that’s why the solution went this way.

[ildar2]

to whom it may concern, my workaround is to make a proxy destination in each module that would be a Destination and use my screen directly:

/**
 * Auxiliary screen to use SearchUserScreen between modules
 * https://github.com/raamcosta/compose-destinations/issues/59
 */
@Composable
@Destination
fun SearchUserProxy(
    resultNavigator: ResultBackNavigator<String>?
) {
    SearchUserScreen(resultNavigator)
}