Hey all. We're starting to land some Kotlin-specific changes into Dagger! Two have already landed which will be in the next release: - Understand qualifier annotations on properties without requiring a use-site target (i.e.,

@Whatever

instead of

@field:Whatever

) - Understand

@Module

on

object

does not require a module instance. We have a few more in the pipeline, but if you have any ideas of small ergonomic improvements like this please file an issue on GitHub.

Is there any chance of ever getting to

@Inject

annotate the class declaration in order to specify the default constructor rather than having to break the constructor out?

The

@Inject

annotation does not allow targeting to types. You'd probably have better luck getting Kotlin to add an annotation use-site target for the primary constructor for class-level annotations.

gotcha, would that be something to post on their YouTrack?

Yes

Thanks. Happy to see some Kotlin QoL improvements in Dagger, though!

So the second one is about static provides?

Yes. Providers on an object will be interpreted as "static" without needing

@JvmStatic

.

The need for

@JvmSuppressWildcards

is significantly decrease ergomonics, especially for lambdas

That's next on my list. Well, first. The listed two things were done by someone else.

typealias as qualifier, but it, I believe, already was reported

Yeah I'm not sure I quite buy that one

Yeah, also not sure about backward compatibility with existing code, but looks still nice to have super simple way to declare qualifiers. But anyway, looks that we use

@Named

much more than annotation because of multi-module project

Rename component and module into something less ambiguous 😉