I have issue with dagger2 using mapkey/intomap and...
# eapn
nitrog42
04/04/2019, 8:39 AMI have issue with dagger2 using mapkey/intomap and Provider<*> for some Android component injection too
I’m feeling something changed in KClass 😄
a
Alexey Belkov [JB]
04/04/2019, 5:01 PMWhat kind of issue? Can you please report it at http://kotl.in/issue with a sample project to reproduce?
n
nitrog42
04/06/2019, 8:56 PMYes sorry, I need to take some time to make a sample project so you guys get the exact error. I’ll try to do it monday, thanks for your work !
👍 2
y
yshrsmz
04/12/2019, 6:13 AMI think I might hit the same issue
n
nitrog42
04/12/2019, 8:28 AMI’m really sorry, I forgot about it/was busy with work, and now it unfortunatelly hit stable release it seems
nitrog42
04/12/2019, 8:31 AMI’ll try to make an issue right now
nitrog42
04/12/2019, 8:50 AMOk i have a (not) working sample. @Alexey Belkov [JB] are you guys comfortable with dagger ? because the sample will be as short as possible but it’s still comes from a dagger architecture....
nitrog42
04/12/2019, 8:56 AMSeems somebody already did a sample : https://github.com/google/dagger/issues/1478
a
Alexey Belkov [JB]
04/12/2019, 9:15 AMThanks, we'll investigate. For reference, the issue is
<https://youtrack.jetbrains.com/issue/KT-30979>n
nitrog42
04/12/2019, 12:50 PMyes I forgot to put it here after 😄 thanks for all your work
2 Views