NEW: Subscribe to Hacking with Swift+ and accelerate your learning! >>

Resolvers and Dependency Injection | Opinions

Forums > Swift

I came across this post on Medium

Swift 5.1 Takes Dependency Injection to the Next Level

And just by chance it was used in a video I watched by the Firebase Firestore Team - was part of this series (which was very good I might add)

I couldnt resist and decided to implement this in one of my existing projects, the results have been really good, and cleaned up the SwiftUI code a great deal.

I have read that Service Locator is considered an anti-pattern as it has known negative effects (e.g., implicit dependencies that will be evaluated at runtime) while better solutions exist (e.g., Constructor Injection). However seems like a really clean way do this and would like to hear opinions of other more skillful developers.

   

Hacking with Swift is sponsored by Paw

SPONSORED Use Paw to build, test and describe web APIs. Paw has a lightning fast native macOS interface to compose requests, collaborate in real-time on API specs, and generate client code for your applications. You can import and export API definitions.

Discover Paw for Mac

Sponsor Hacking with Swift and reach the world's largest Swift community!

Reply to this topic…

You need to create an account or log in to reply.

All interactions here are governed by our code of conduct.

 
Unknown user

Not logged in

Log in
 

Link copied to your pasteboard.