Use Dagger `Qualifier` instead of `Named` about simple-android HOT 5 CLOSED

Proposal 2 seems fairly easier to maintain but with this we'd still use Named annotation across the project. So the purpose of the issue still remains, right?

Kind of, the main thing we are trying to do is avoid having to type the name for the Named parameter while injecting since it's not type-safe and it's prone to developer error.

I kind of like the qualifier approach since we are removing the usage of primitives and adding information via a type itself. Maintaining a bunch of different annotations isn't that much overhead over maintaining a list of constants, IMO. In addition the qualifiers are compile time only (correct me if I am wrong here) so it won't have any impact on our build.

from simple-android.

I kind of like the qualifier approach since we are removing the usage of primitives and adding information via a type itself. Maintaining a bunch of different annotations isn't that much overhead over maintaining a list of constants, IMO. In addition the qualifiers are compile time only (correct me if I am wrong here) so it won't have any impact on our build.

Yes, it will behave the same way Named behaves so it should not affect our builds anymore than Named.

from simple-android.

Qualifier Proposal +1

from simple-android.

Proposal 2 seems fairly easier to maintain but with this we'd still use Named annotation across the project. So the purpose of the issue still remains, right?

from simple-android.

Proposal 2 seems fairly easier to maintain but with this we'd still use Named annotation across the project. So the purpose of the issue still remains, right?

Kind of, the main thing we are trying to do is avoid having to type the name for the Named parameter while injecting since it's not type-safe and it's prone to developer error.

from simple-android.