Hi everyone, I am using v2.1.0(beta 09) version an...

# compose-destinations

[Aseem Sharma]

Hi everyone, I am using v2.1.0(beta 09) version and vanilla NavHost while implementing compose destination in a multi module project, we need to specify @Destination<RootGraph> for a feature level entry screen, my question was why do we have Annotation as compulsory type of @Destination, I can see some code snippets in the doc where @Destination is used as follows:

@Destination(
    visibility = CodeGenVisibility.INTERNAL // or PUBLIC
)
@Composable
internal fun MyScreen() { /*...*/ }

I cannot use it same way while declaring destination on my side, I have to mention RootGraph

[Rafael Costa]

Hi 👋
This was a change made on v2.
The docs you’re mentioning, are they part of v2 docs or v1? If they’re from v2, they need fix.

[Aseem Sharma]

Here we are having feature modules and each feature module has a entry point I don’t want to have multiple navGraphs for each feature, I have manually turned off generation of NavGraph:

arg("compose-destinations.generateNavGraphs", "false")

only then I am able to use single navGraph, if I remove this setting and build I get following error:

[ksp] com.ramcosta.composedestinations.codegen.commons.IllegalDestinationsSetup: NavGraph 'RootGraph' doesn't have any start route. Use corresponding annotation with `start = true` in the Destination or nested NavGraph you want to be the start of this graph!

start = true I have already declared in app module splash screen, since @RootGraph is used in feature module which may not be accessible to the library hence this error is thrown, if you can suggest any solution to this it will be very helpful. TIA

[Rafael Costa]

Have you checked this?
https://composedestinations.rafaelcosta.xyz/v2/multi-module-setup/

[Rafael Costa]

It is specifically about this topic

[Rafael Costa]

Quick hint is that you probably don’t want to use RootGraph on feature modules. You want to create your own graph and use it in that feature module. Then include it back in the main module as a nested graph. The link above also explains how to do these things 🙂

[Rafael Costa]

I actually don’t remember from the top of my head what happens if you use RootGraph in feature modules.. but either it won’t work or it will just be considered its own graph (maybe with the name of the module set on gradle ksp block) and that’s why it’s telling you you need a start destination. All graphs need a start even nested graphs.

[Rafael Costa]

Either way, it’s better if you create your own like I said before.

[Aseem Sharma]

Yes I got this now, I was thinking earlier to have it simple by just using ExternalModuleGraph but you are right I have to include feature level navGraphs, with their public destination as start true, I will refactor this on my side, thanks for clearing up the confusion 👍