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
-
The CS answer is The Dependency Inversion Principle (the D of SOLID). Relying on abstractions, using a DI framework and whatnot. In reality I think you'd want the interface as a way to force consistency when you inevitably add a second Repository and you want the two to match
"when you inevitably add a second Repository and you want the two to match" 
I have never had to do that.
And even if you did have to do it, what's the problem of extracting an interface *at that point* rather than before.
-
-
The inevitability depends on scale I guess. If you're certain you'll never need a second repo then don't bother.
-
The only harm I can see in creating the interface later is that it'd mean a change to a bunch of unrelated code. You'd have to update other places to rely on the new interface instead of the class. I guess it's planning for a possibly complex future or thinking YAGNI.
- Pokaż odpowiedzi
Nowa rozmowa -
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.