schwarzit / kokain Goto Github PK

It is possible to call multiple times the constructor of Beans marked as singleton, which leads to undocumented behaviors and crashes. Make SingletonScope Thread safe

In some usecases it would be useful if there's no need to know the exact implementing class of a Bean. Therefore the possibility to inject the implementation into a property of the type of an interface would be useful
example:

Printer -> PrinterImpl, MobilePrinterImpl

Implementation Idea:

1.) New Annotation called @EInterface(Class<*>) this class can be a EBean or a Mapper
2.) Provide Mapper Interface which have a fun map(Class) : Class
3.) In that Interface implementation the Interface type could be mapped to the exact implementation by the requirements

For now, there is no way to inject ViewModel along with ViewModelProvider, it would be nice to have ktx extension named like by viewmodel() in order to have a fully injected ViewModel lifecycle.