NEW: Start my new Ultimate Portfolio App course with a free Hacking with Swift+ trial! >>

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 Fernando Olivares

SPONSORED Would you describe yourself as knowledgeable, but struggling when you have to come up with your own code? Fernando Olivares has a new book containing iOS rules you can immediately apply to your coding habits to see dramatic improvements, while also teaching applied programming fundamentals seen in refactored code from published apps.

Try the book!

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

Archived topic

This topic has been closed due to inactivity, so you can't reply. Please create a new topic if you need to.

All interactions here are governed by our code of conduct.

Unknown user

You are not logged in

Log in or create account

Link copied to your pasteboard.