Dependency Injection in Swift using latest Swift features
Dependency Injection is a software design pattern in which an object receives other instances that it depends on. It’s a commonly used technique that allows reusing code, insert mocked data, and simplify testing. An example could be initializing a view with the network provider as a dependency.
There are many different solutions for dependency injection in Swift, which all have their own pros and cons. It turned out to be a very opinionated topic when I asked on Twitter which solution engineers prefer to use. Before diving into my solution today, it’s good to know many good solutions exist. It’s not a given my solution works for everyone, so feel free to explore the world of dependency injection and find the one that fits you best.FREE iOS Architect Crash Course for a limited time! If you’re a mid/senior iOS developer looking to improve your skills and salary level, join this 100% free online crash course. It's available only until March 26th, so click to get it now! Dependency Injection without 3rd party library
My approach, in general, is to find solutions in Swift that take away the requirement of a 3rd party library. An external library makes it easy and faster to get started right away. However, it might also be too tempting just to get started with an external library while combining a few of Swift’s powerful features would have been enough too.
