My situation
I have a large app where all screens live in a single :app module, organized by feature packages (e.g. feature.feed, feature.profile, feature.settings, …) rather than by Gradle module. This was a so long architectural decision, and migrating to feature modules isn't an option for us, there are multiple constraints that rule out that kind of refactor.
The problem: with this setup, the graph always renders the whole app at once. With this many screens that's hard to read and review. What I'd really like is to view/export the graph one feature at a time.
My question
From the docs, it looks like all the scoping options (aggregate, scopes, @NavGraphRoot) are tied to module boundaries, so there's no way to scope by package within a single module today. Am I right that this isn't currently possible?
If so, is supporting this kind of intra-module / package-level scoping something you'd consider adding to the roadmap?
Thanks!
My situation
I have a large app where all screens live in a single
:appmodule, organized by feature packages (e.g.feature.feed,feature.profile,feature.settings, …) rather than by Gradle module. This was a so long architectural decision, and migrating to feature modules isn't an option for us, there are multiple constraints that rule out that kind of refactor.The problem: with this setup, the graph always renders the whole app at once. With this many screens that's hard to read and review. What I'd really like is to view/export the graph one feature at a time.
My question
From the docs, it looks like all the scoping options (
aggregate, scopes,@NavGraphRoot) are tied to module boundaries, so there's no way to scope by package within a single module today. Am I right that this isn't currently possible?If so, is supporting this kind of intra-module / package-level scoping something you'd consider adding to the roadmap?
Thanks!