Static class or regular class with interface?
Hello,
I've been building a QR code generator for a while. It's a simple method call
It is a static method/class, I was wondering if it would be better to supply the class trough an interface, making it available trough DI. Suppose it's going to be a nuget package, would it make a difference if it was supplied trough DI, instead of a static class?
I've been building a QR code generator for a while. It's a simple method call
QrCodeGenerator.Generate("data", options).It is a static method/class, I was wondering if it would be better to supply the class trough an interface, making it available trough DI. Suppose it's going to be a nuget package, would it make a difference if it was supplied trough DI, instead of a static class?