@evant Do you have any plans to add something like Dagger's

fun inject(someActivity: SomeActivity)

...? It's SO MUCH nicer than having to do the trick in the Android docs on kotlin-inject's Github repo...

No plans to add field or function injection. It can leave objects in a partially constructed state which can cause runtime issues if you aren't careful. Pulling your logic out of your activity also makes it easier to test.

What difference is it from:

class MyActivity : Activity() {
    private lateinit var myScreen: MyScreen

    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate()
        myScreen = ActivityComponent::class.create(ApplicationComponent.getInstance(this)).myScreen

All the important bits are in MyScreen which you can easily construct and unit test

I was really considering to use kotlin-inject instead of Hilt for a bigger module in our app... but I have a bunch of workmanagers that need to be injected with multiple deps, and that could get a bit messy. That separation I do already in what I'm injecting... but I need to manually give all those to each workmanager... which is a lot of boilerplate...

https://developer.android.com/reference/androidx/work/WorkerFactory ? Could do the same thing that's suggested for fragments

@evant it says kotlin-injeft

Lol