This message was deleted.
# multiplatform
s
This message was deleted.
h
Not really. Usually that androidMain contains native code that is not availabe in your shared/common module. For example to get context, you have to have an expect method in shared/common and have its actual overriden in androidMain. From what you shared, data module depends on domain module, this is wrong and should be in reverse order
So if you want to build separate data, domain module, they are all should be in common/shared module, assuming that all dependencies of these module support KMP or have native specific feature overriden in androidMain, iOSMain,..
👀 1
h
Then, how i can make specific sourceSet (not common) can access to common sourceSet of other module?
h
You can do it. You can take a look at this repository, it comes with feature-based approach and has some feature dependency. https://github.com/supabase-community/supabase-kt
🙌 1
h
dependencies {
addModules(SupabaseModule.AUTH, SupabaseModule.SUPABASE)
}
You mean:
addModules
right?