Approach on UserComponent using entry points

[manuelvicnt]

This is a way to "insert" a component in the middle of the hierarchy.

You create a custom component as specified in the docs and access it with an entry point. As any Component needs to have a lifecycle owner, you can make that owner implement the GeneratedComponentManager interface and use an instance of it in the EntryPoints.get method.

In this case, UserComponent is managed by UserManager (which implements GeneratedComponentManager). When an object scoped to that component is needed, then the UserManager is injected into that class and the scoped type is retrieved using an entry point. UserDataRepository is scoped to UserComponent, that's what the presenters take in as a dependency. UserComponent's parent is ApplicationComponent so we're using it as a Component in the middle of application and activity components.

Current code:

• This example uses AssistedInject but it's not necessary.
• This solution uses Presenters instead of ViewModels but you can get them to work as shown in this gist.

Caveats:

• This solution works well when the user has a sign-in and sign-out flow. If there's account switching while the user is on the same screen, then you need a way to restart the activity/fragment the user is in.

[Zhuinden]

Hmm, internal?

[manuelvicnt]

If you want to avoid this, you can remove the GeneratedComponentManager interface from UserManager and pass the userManager.userComponent to the entry point. It's the same

[manuelvicnt]

Created google/dagger#1948 to get this addressed :)