Describe the bug
I'm not sure if this is a bug or not and I'm sure I'm not the first to notice this, but it's about string parameters. If a class has a string parameter in the constructor, I would expect the DI to fail if there is no string parameter provided in any koin module, but instead it succeeds. As mentioned in other threads, I believe this is because if there is no adequate dependency in any module, koin defaults to an empty string? Please let me know if this makes sense or if more context is needed.
To Reproduce
Go to Android Studio and create a sample project with Koin as a dependency
Create a class with a string parameter in the constructor, such as:
class Test(private val testString: String)
Create a koin module which provides the class but not a string parameter:
val testModule = module {
singleOf(::Test)
}
Create a test which calls koinApp.checkModules()
Expected behavior
Expected behavior would be for the koin test to fail because there is no string dependency provided in any koin module, but instead it succeeds.
Koin module and version:koin-android:3.4.3koin-android-test:3.4.3
Describe the bug I'm not sure if this is a bug or not and I'm sure I'm not the first to notice this, but it's about string parameters. If a class has a string parameter in the constructor, I would expect the DI to fail if there is no string parameter provided in any koin module, but instead it succeeds. As mentioned in other threads, I believe this is because if there is no adequate dependency in any module, koin defaults to an empty string? Please let me know if this makes sense or if more context is needed.
To Reproduce
koinApp.checkModules()
Expected behavior Expected behavior would be for the koin test to fail because there is no string dependency provided in any koin module, but instead it succeeds.
Koin module and version:
koin-android:3.4.3
koin-android-test:3.4.3