Chris Banes

Why do we need typealiases at all? Can we not rely on qualifiers entirely like Dagger? ``` kotlin @Component abstract class MyComponent { @Provides @Named("foo") fun fooDep(): Dep = Dep(...)...

We ended up enabling the [javax.inject](https://github.com/evant/kotlin-inject#options) support for this, but as we're building for KMP I had to create a 'fake' `javax.inject.Qualifier` class. ``` kotlin package javax.inject annotation class Qualifier...

I like option 2. Can always disable one of the option if it becomes a problem in the future

> Hm, would limiting each type to one qualifier be reasonable? I'd say yes. You can always create your own composite qualifier if you need (I think)

I'm afraid that Insetter is basically in maintenance mode. Feel free to submit PRs though if you want to fix it yourself.

Looks like a version mismatch. Are you using Compose Multiplatform [1.7.0-alpha01](https://github.com/JetBrains/compose-multiplatform/releases/tag/v1.7.0-alpha01)? 1.7.0-alpha02 might work but I haven't tried it yet.

Working fine for me, so without a reproducing sample there's not much I can do. Try [0.9.0-alpha06](https://github.com/chrisbanes/haze/releases/tag/0.9.0-alpha06) which is built against CMP 1.7.0-alpha02. You might also want to clear out...

I'm going to close this, as I think this is user-specific issue.

Do you have any sense of how much work is involved? I'd like to see a bit more progress before landing this personally, as I think there's going to be...

> Think most of the work is in supporting seekable transitions for predictive back, then maybe building some simpler api's on top of that? Sounds good to me! I just...