Using superinterfaces generates invalid component. about auto-dagger2 HOT 4 OPEN

Yes it cannot work like that.
superinterfaces is a no brainer that adds the extends Interface on the generated component.

I didn't add the support for extending a component because I think it's not something that you would do. If the parent component contains some inject(...) methods, you don't want to inherit them, but only the exposed dependencies.

What I do is to create the exposed dependencies in a separated interface.

public interface ApplicationDependencies {
   MyDep1 myDep1();
   MyDep2 myDep2();
}

@Component
public interface ApplicationComponent extends ApplicationDependencies {
   void inject(Application app);
}

The children components will extend the ApplicationDependencies and not the component itself. Like this you avoid to inherit the method void inject(Application app)

@Component(dependencies = ApplicationComponent.class)
public interface ActivityComponent extends ApplicationDependencies {
   void inject(Activity activity);
}

And with auto component:

@AutoComponent(dependencies = ApplicationComponent.class, superinterfaces = ApplicationDependencies.class)
public class MyActivity extends Activity {

}

I'm assuming this is the right way to do it, but I may be wrong.

from auto-dagger2.

Gotcha. Okay I guess you're right in this use case but I won't necessarily have an inject method to inherit, so it might be okay to support it - I mean I don't think this library should impose the way you write DI classes, but give you the power to mix it up a bit.

Thanks, great library:)

from auto-dagger2.

Valid point.
I'll include the support in the next version, beginning of January, as I'm quite busy right now.
Thanks for the feedback!

from auto-dagger2.

+1 for that feature

from auto-dagger2.