What do you think in a project multi-module have f...

# android-architecture

[Joan Colmenero]

What do you think in a project multi-module have for instance
app
core(or whatever)
feature1
feature2
feature3
navigation <--

I'm planning to implement navigation to a multi-module project and is it a good praxis to create a navigation module which is included on each feature and inside of it contains all of the navigation between features?

[allan.conda]

That works, but you cannot use parcelable classes declared in the feature modules as nav arguments

[allan.conda]

I know since we follow that approach

[allan.conda]

feature module will depend on navigation, so navigation can’t depend back due to circular dependency

[allan.conda]

you would have to define these nav args within the navigation module itself as well

[allan.conda]

and also if you’re using Jetpack Navigation, you’ll see reds on the Fragment classnames since you don’t have direct access to it. It still works however

[sajadgarshasbi]

yes, you can declare all parcelable classes and navigation resources in navigation module, then all features can navigate between each other

[Joan Colmenero]

Thanks 😄