Does it possible to lock the Koin modules and dependency in some sort of `:koin-bridge` module as we...

# koin

[miqbaldc]

Does it possible to lock the Koin modules and dependency in some sort of :koin-bridge module as well?

Related: https://link.medium.com/YNApqhYurnb

To avoid leaking API of such data layer in the application layer. So the modules provider exist in the :koin-bridge, the koin-bridge will depend on domain, & data (for concrete implementation of domain repository)

And our application/presentation layer will depends on koin-bridge instead of depends directly :data layer

[arnaud.giuliani]

the only limit is compile visibility. Behind that you can access the Koin container, and request the needed type

[miqbaldc]

Behind that you can access the Koin container, and request the needed type

Sweet!

[miqbaldc]

he only limit is compile visibility.

Does this limitation only exist in koin-annotations as of now? or did you mention different meaning for compile visibility?

[arnaud.giuliani]

compile in the sense of Gradle module, nothing more

[miqbaldc]

Ah, that’s explain everything, thanks for confirming!

[miqbaldc]

It’s recommended to unit check missing provided module(s) using checkModules API cmiiw? As Koin doesn’t have impact to the build time (or no compile visibility) in this case for :koin-bridge module

[arnaud.giuliani]

yes checkModules allow to quickly test a Koin dependency graph