0x3333 / dagger-aop Goto Github PK

Currently, we return Strings and print errors, we could do something like Dagger has did, ValidationReport.

Create the LogInterceptor in real code.

We could generate a dagger module class binding the new generated classes to the original implementation.

This way users could just bind the interface or abstract class to their implemented classes the way the generally would. The only required step would be to add this new module in their modules.

User module just includes our new generated module:

@Module(includes = { DaggerAopModule.class }) // Includes DaggerAopModule
public abstract class SomeModule {

    @Binds
    abstract ConcreteInterface providesSomeInterface(Concrete impl);

}

This is our generated module:

/**
 * This is the generated dagger-aop module.
 */
@Module
public abstract class DaggerAopModule {

    @Binds
    abstract Concrete providesSomeInterface(Interceptor_Concrete impl);

}

Would be nice to separate the project in two:

• _Core_ - Inclunding only the interfaces and public stuff.
• _Compiler_ - Code that are used only to generate classes.

The runtime dependency would be smaller. The same way dagger do.