Needle is a dependency injection (DI) system for Swift. Unlike other DI frameworks, such as Cleanse, Swinject, Needle encourages hierarchical DI structure and utilizes code generation to ensure compile-time safety. This allows us to develop our apps and make code changes with confidence. If it compiles, it works. In this aspect, Needle is more similar to Dagger for the JVM.
Needle aims to achieve the following primary goals:
- Provide high reliability by ensuring dependency injection code is compile-time safe.
- Ensure code generation is highly performant even when used with multi-million-line codebases.
- Be compatible with all iOS application architectures, including RIBs, MVx etc.
Using Needle to write DI code for your application is easy and compile-time safe. Each dependency scope is defined by a Component. And its dependencies are encapsulated in a Swift protocol. The two are linked together using Swift generics.
/// This protocol encapsulates the dependencies acquired from ancestor scopes.
protocol MyDependency: Dependency {
/// These are objects obtained from ancestor scopes, not newly introduced at this scope.
var chocolate: Food { get }
var milk: Food { get }
}
/// This class defines a new dependency scope that can acquire dependencies from ancestor scopes
/// via its dependency protocol, provide new objects on the DI graph by declaring properties,
/// and instantiate child scopes.
class MyComponent: Component<MyDependency> {
/// A new object, hotChocolate, is added to the dependency graph. Child scope(s) can then
/// acquire this via their dependency protocol(s).
var hotChocolate: Drink {
return HotChocolate(dependency.chocolate, dependency.milk)
}
/// A child scope is always instantiated by its parent(s) scope(s).
var myChildComponent: MyChildComponent {
return MyChildComponent(parent: self)
}
}This is pretty much it, when writing DI code with Needle. As you can see, everything is real, compilable Swift code. No fragile comments or "annotations". To quickly recap, the three key concepts here are dependency protocol, component and instantiation of child component(s). Please refer to the Getting started with Needle section below for more detailed explanations and advanced topics.
Using and integrating with Needle has two steps. Each of the following steps has detailed instructions and explanations in the linked documents.
- Integrate Needle's code generator with your Swift project.
- Write application DI code following NeedleFoundation's API.
Needle has two parts, the NeedleFoundation framework and the executable code generator. Both parts need to be integrated with your Swift project in order to use Needle as your DI system.
Using Carthage
Please follow the standard Carthage installation process to integrate the NeedleFoundation framework with your Swift project.
github "https://github.com/uber/needle.git" ~> VERSION_OF_NEEDLE
Using Swift Package Manager
Please specify Needle as a dependency via the standard Swift Package Manager package definition process to integrate the NeedleFoundation framework with your Swift project.
dependencies: [
.package(url: "https://github.com/uber/needle.git", .upToNextMajor(from: "VERSION_NUMBER")),
],
targets: [
.target(
name: "YOUR_MODULE",
dependencies: [
"NeedleFoundation",
]),
],
Using CocoaPods
Please follow the standard pod integration process and use NeedleFoundation pod.
Using Carthage
If Carthage is used to integrate the NeedleFoundation framework, then a copy of the code generator executable of the corresponding version is already downloaded in the Carthage folder. It can be found at Carthage/Checkouts/needle/Generator/bin/needle.
Using Homebrew
Regardless of how the NeedleFoundation framework is integrated into your project, the generator can always be installed via Homebrew.
brew install needle
The linked document uses a somewhat real example to explain what the dependency injection pattern is, and its benefits.
If you like Needle, check out other related open source projects from our team:
- Swift Concurrency: a set of concurrency utility classes used by Uber, inspired by the equivalent java.util.concurrent package classes.
- Swift Abstract Class: a light-weight library along with an executable that enables compile-time safe abstract class development for Swift projects.
- Swift Common: common libraries used by this set of Swift open source projects.
