I guess the only downside to such an interface wou...

# kotlin-inject

[dave08]

I guess the only downside to such an interface would be that the actual repository fakes might have extra methods to help in testing, which would make us define the fake's dep. plus the alias to the interface it implements... if @Inject would automatically create the provider, then only the binding would be left... but even then, the component would need to provide it somehow too...