Should the Configurator be singleton?
onmyway133 opened this issue · comments
You said that "There should be only one configurator for each scene, and the connection setup code should run once and only once" (http://clean-swift.com/clean-swift-ios-architecture/)
Why not let it be instance? Just create it (or DI) and let it do the job?
+1 for DI, but no singletons pls.. let's keep it clean ;)
I wonder if we can build a DI mechanism into Clean Swift like this:
https://github.com/orakaro/Pure-Swift-Dependency-Injection