module graph assert to make sure feature modules don't depend on other feature modules

[lydavid]

https://github.com/jraska/modules-graph-assert

[lydavid]

if feature modules contain more than just ui, is there anything wrong with them depending on one another?

[lydavid]

With circuit, a feature that may navigate to another feature just needs to sink an event to navigate to that screen. Even before circuit, we had a Destination enum for that.

Common ui shouldn't be in feature modules

[lydavid]

Other projects would extract the common ui out to a common module, then have each of the feature module depend on that

[lydavid]

Another approach is to have feature-impl and feature-api, where feature modules may depend on the api for other modules but not its impl.