Fellow devs - if you have a "repository"-like object that only has a single implementation do you do this? If so - why?pic.twitter.com/GRogvFc7qu
Pokaż ten wątek
-
In my opinion it's much better to avoid the needless interface and just do this instead. Before anyone mentions tests and mocking - good mocking frameworks can mock classes no problem - you don't need an interface, so what else is it?pic.twitter.com/oS1pA6ddlq
Pokaż ten wątek
Really nice to see the variety of answers on this thread. I think this is broken down into two use cases:
If you are building a monolith or you know there'll only be a single implementation - do not use an interface
If you are building multi-module you need an interface
-
-
The only argument for using an interface for testing I've seen is when using Kotlin native, where you can't mock a final class.
I still haven't seen a good explanation of why mocking a class when you're just writing for the JVM is bad though. Anyone?Pokaż ten wątekDziękujemy. Twitter skorzysta z tych informacji, aby Twoja oś czasu bardziej Ci odpowiadała. CofnijCofnij
-
Wydaje się, że ładowanie zajmuje dużo czasu.
Twitter jest przeciążony lub wystąpił chwilowy problem. Spróbuj ponownie lub sprawdź status Twittera, aby uzyskać więcej informacji.