[Gradle] Koin Gradle Plugin - check your modules
See original GitHub issueHi all,
while I’m looking at Arrow Meta to help leverage some tooling, what do you think of having a Gradle plugin to allow you to verify your Koin configuration via Gradle?
I would imagine something like this, in your gradle:
koin {
modules = ["com.myapp.myModule1","com.myapp.myModule2"]
}
and having a task like ./gradlew checkKoinModules
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:10 (8 by maintainers)
Top Results From Across the Web
io.insert-koin : koin-gradle-plugin : 3.1.2 - Maven Central
koin -gradle-plugin - KOIN - Kotlin simple Dependency Injection Framework.
Read more >Verifying your Koin configuration
Koin allows you to verify your configuration modules, avoiding to discover dependency injection issues at runtime.
Read more >Setting up Koin 2.0.1 for Android | by Matti Mäki-Kihniä | Medium
Koin is a dependency injection framework. Version 2.0 was recently released, but it's still a bit tricky to find all the information in...
Read more >kotlin - Gradle problems of adding koin test dependencies
It looks like there are 3 problems. As I mentioned in the comment, the Kotlin JVM and Serialization plugins have mismatched versions.
Read more >Learning the Basics - Gradle User Manual
The location for storing modules is called a repository. By declaring repositories for a build, Gradle will know how to find and retrieve...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The original checkModules implementation did something like that but it gave false positives. A problem with most solutions is that you need to compile the code itself in order to check it, which is (from performance standpoint) a no-go. A linter could work but writing one that transitively checks all modules, with parameters and qualifiers, is going to be a challenge.
can you remove this?