Using Type Erasure to Build a Dependency Injecting Routing Framework in Swift

20 January 202018 July 2021 patmcg1 Comment

This post is just as weird and abstract as it sounds. 🤯 On first pass, I don’t get it. But I’m saving it here because I always like anything that promises easier dependency injection.

We’ll take an exciting look at how the treatment of methods/closures as properties can be used in this context to bypass one of the Swift Compiler’s most annoying compilation errors.

👉 Using Type Erasure to Build a Dependency Injecting Routing Framework in Swift

Type Erasure is the process of abstracting constrained, generic types inside an unconstrained non-generic type that can be passed around freely

Via iOS Dev Weekly.

Software Dev

Swinject: lightweight dependency injection in Swift

13 July 201918 July 2021 patmcg1 Comment

Looks like promising way to do DI in swift. If you think you really need a framework anyways. 🤷🏻‍♂️

👉 Swinject: a lightweight dependency injection framework for Swift

Software Dev

iOS: Dependency injection in Swift

13 July 201918 July 2021 patmcg2 Comments

This very brief and somewhat vague article makes the case that DI in Swift can be simple and doesn’t need a third-party dependency.

👉 iOS: Dependency injection in Swift

Or try Swinject? This article also pointed me to a good quote.

Software Dev

Dependency Injection in a Sentence

13 July 201918 July 2021 patmcg2 Comments

Dependency Injection seems so confusing and counterintuitive at first, so I love this quote which pretty well summarizes and demystifies it.

Dependency injection means giving an object its instance variables. Really. That’s it.
Dependency Injection Demystified

Software Dev

DI with Interface Builder

29 April 201918 July 2021 patmcg1 Comment

In this dated but thorough Objective-C dependency injection article is a reference to a rather old article asserting that Xcode’s Interface Builder is their “favorite di framework of all time”.

👉 Dependency Inversion Principle and iPhone

I keep feeling frustrated by the added complexity and extra code involved in dependency injection. It can make simple code complex very quickly. So I really love the idea here, which is that Xcode is perfect for DI because it lets you literally just wire up things visually with no extra code. It goes on to make the case for using Interface Builder to wire up more than just UI elements and use it for just about anything.

What’s great about it is that it doesn’t just generate a bunch of code, but instead “freeze dries” real objects to be instantiated when the program loads.

This article is so old that the images don’t load, but I love the ideas and the reminder that DI does not have to involve a bunch of extra code. Thanks to iOS Dev Weekly for the initial link. 👆