You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Especially for someone newer to multi-modular apps, looking at all the modules on the top level of the project can be daunting.
Describe the solution
It would be awesome if an always up-to-date graph of how the modules depend on each other could be shown in the README of this repository.
Additional context
I was recently reading the article "Jetpack Compose — Before and after" from Chris Banes and in that post, the section "The app" with the figure named "Graph of Tivi’s module structure. Generated using Jake Wharton’s handy Gradle task" is exactly what I am talking about. I hope you can refer to it for some inspiration.
This would give a visualization of how everything is structured in an instant without having to look at the gradle files of all modules.
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Describe the problem
Especially for someone newer to multi-modular apps, looking at all the modules on the top level of the project can be daunting.
Describe the solution
It would be awesome if an always up-to-date graph of how the modules depend on each other could be shown in the README of this repository.
Additional context
I was recently reading the article "Jetpack Compose — Before and after" from Chris Banes and in that post, the section "The app" with the figure named "Graph of Tivi’s module structure. Generated using Jake Wharton’s handy Gradle task" is exactly what I am talking about. I hope you can refer to it for some inspiration.
This would give a visualization of how everything is structured in an instant without having to look at the gradle files of all modules.
Code of Conduct
The text was updated successfully, but these errors were encountered: