Working with dagger on a larger team. What do you ...

# dagger

[Colton Idle]

Working with dagger on a larger team. What do you all do to ease "onboarding" of someone that is familiar with dagger but we have so many Types available to inject, it can be hard to find. Do you recommend just listing out what "bindings" are available? Or is there something else that's clever that I haven't thought of?

[Halil Ozercan]

Android Studio 4.1 should have dagger navigation support where inject, provides, or bindings are defined. It's nowhere near perfect but might be useful for new comers.

Also, if they are already familiar with Dagger, they shouldn't have hard time finding related dependencies in a codebase. I find it useful to have a graph of high level bindings between components and modules that summarizes the general architecture of your Dagger setup. Details should be discovered by individuals by simply navigating the code 🤷

[Colton Idle]

"Details should be discovered by individuals by simply navigating the code" AGREE!

"I find it useful to have a graph of high level bindings between components and modules that summarizes the general architecture of your Dagger setup."
That's exactly what I want. I think I might create my own graph for high level bindings and indicate that there may be more but the graph/chart is purely informational.

[radityagumay]

correct, what i usually do is that provide a example app that contains how do we construct our dependencies in the main-app.

so that new engineer able to learn from the example app first, before she/he go through the main-app.

and latest IDE as navigation graph for dagger it should help the engineer to dive in in order get more knowledge.

@Colton Idle

[Colton Idle]

interesting. a sample app for exploring dependencies. thanks @radityagumay