Andreas Nomikos

motif usage with kaptish forces using @JvmSuppressWildcards to be able to match types between providers and consumers **0.3.2 with kaptish**: **Repro steps or stacktrace**: ``` // Provider @motif.Objects @Suppress("detekt.UnnecessaryAbstractClass") abstract...

Feature Request: Motif Scopes should automatically provide all the interfaces that they implement as bindings within the scope

2

A common and useful pattern is as follows ``` public class Foo(ParentComponent) { public interface ParentComponent { Bar bar() } } ``` This pattern allows every single class that defined...

Feature Request: Provide a builder method for "root" motif scopes

1

This is an extension to #52 with a slightly different and more generic use case. if you are trying to decompose motif scopes in multiple libraries as in the case...

Motif should handle presence of ErrorType gracefully

3

When running motif in incremental compilation build setting the motif compiler tends to crash out frequently whenever it encounters an ErrorType. Instead motif should defer parsing structures that contain error...

Motif promotes a coding model comprised of a big tree of small nested scopes so using some form of Lazy is usually not required. javax.inject.Provider can be a direct standin...

javax.inject.Provider has been a staple of all known DI frameworks. Motif should also automatically provide the Provider dependency whenever the Foo dependency is declared