ok nice. I have a component that should die with m...
# androidl
Lilly
03/27/2019, 8:45 PMok nice. I have a component that should die with my fragment. Should I instantiate this component in application as singleton and provide it in my fragment or should I instantiate it in fragment everytime it is started?
@jw oh the question isn't Kotlin specific at all ^^ but I would appreciate some help
t
tseisel
03/27/2019, 8:51 PMDo you use
dagger-androidl
Lilly
03/27/2019, 9:01 PMno I often read in tutorials that one can get along without it and that its not necessary but I don't know why yet. My journey just started ^^
t
tseisel
03/27/2019, 9:27 PMJust like RxJava, Dagger is a marvellous tool that can make your life a lot easier when correctly used, but they are also known for their steep learning curve.
As a starting point, I suggest you to have a look at this sample project (this uses dagger-android) : https://github.com/googlesamples/android-architecture/tree/todo-mvp-dagger
tseisel
03/27/2019, 9:30 PMAlso, I you really want to tame the beast, I recommend reading this awesome series of blog posts : https://proandroiddev.com/dagger-2-android-defeat-the-dahaka-b1c542233efc
l
Lilly
03/27/2019, 9:49 PMI will check this out and come back 🙂
g
ghedeon
03/27/2019, 10:42 PMdagger-androida
arekolek
03/28/2019, 7:53 AMI hope you’re not saying that you can’t scope the component when using
dagger-androidl
Lilly
03/28/2019, 11:37 AMI read the whole series and also I had a further look into the dagger documentation and indeed some questions get answered. But I still don't understand why not to use
dagger-androiddagger-androiddagger-androidsubcomponents2 Views