Practical Structure to Configure Dependency Injection in Swift for iOS

!ZPJDIJUHZ Practical Structure to Conﬁgure Dependency Injection in iOS/Swift Yoichi
Tagaya Swift & Fika, 10 September, 2018

!ZPJDIJUHZ Yoichi Tagaya, from Tokyo, Japan About me

!ZPJDIJUHZ Tokyo evening view 1IPUPCZ D 5PNP:VO IUUQXXXZVOQIPUPOFU

!ZPJDIJUHZ About me as Swinject author • Swinject: dependency injection
framework for Swift • Maintained by 5 members • Recently by Jakub Vano especially! • 2,6k+ GitHub stars now and 1k clones everyday • 4 extensions provided

!ZPJDIJUHZ Agenda • Software architecture • Dependency injection (DI) •
Swinject (DI container)

!ZPJDIJUHZ What is software architecture

!ZPJDIJUHZ What is software architecture IUUQTXXXJCNDPNEFWFMPQFSXPSLTSBUJPOBMMJCSBSZGFCFFMFTJOEFYIUNM

!ZPJDIJUHZ Peter Eeles says An architecture • Defines structure and
behavior • Focuses on significant elements • May conform to an architectural style • Influences team structure (inverse Conway maneuver) • Balances stakeholder needs • Is influenced by its environment • Embodies decisions based on rationale

!ZPJDIJUHZ Architecture is not static but dynamic .7$ "SDIJUFDUVSF :FBST
TJODFMBVODI .77. 7*1&3 &YBNQMFPGBQSPEVDU 3*#T &OHJOFFST 6TFST L . .

!ZPJDIJUHZ Architecture is not static but dynamic $ # "
/PX

!ZPJDIJUHZ Architecture is not static but dynamic $ # "
/PX $ /FX# " $ % -BUFS

!ZPJDIJUHZ Production / unit test $ # " 1SPEVDUJPO

!ZPJDIJUHZ Production / unit test $ # " 1SPEVDUJPO 6OJU5FTU
.PDLTUVC PG# "

!ZPJDIJUHZ We need ﬂexibility in architecture

!ZPJDIJUHZ How to make architecture ﬂexible? Dependency injection!

!ZPJDIJUHZ Because dependency injection is glue but sticky-like glue 5JHIU$PVQMJOH
-PPTF$PVQMJOH

!ZPJDIJUHZ How to make the sticky-like glue?

!ZPJDIJUHZ SOLID principles • S - Single responsibility principle •
O - Open/closed principle • L - Liskov substitution principle • I - Interface segregation principle • D - Dependency inversion principle • Should not depend on concretions but abstractions

!ZPJDIJUHZ Depending on concretions / abstractions Depending on concretions (tight
coupling) *NQMFNFOUBUJPO $PODSFUF5ZQF Depending on abstractions (loose coupling) 3FGFSFODF *NQMFNFOUBUJPO Protocol (Interface) 3FGFSFODF $PODSFUF5ZQF" $PODSFUF5ZQF#

!ZPJDIJUHZ Dependency injection: a way to realize dependency inversion principle
*NQMFNFOUBUJPO Protocol (Interface) 3FGFSFODF *OTUBODFPG $PODSFUF5ZQF# 1BTT JOKFDU UPJOJUJBMJ[FS $PODSFUF5ZQF# 5IFTZTUFNJTDPOpHVSFE UPVTF$PODSFUF5ZQF#

!ZPJDIJUHZ Code example of dependency injection protocol APIClientProtocol { ...
} class APIClient: APIClientProtocol { ... } let vm = MyViewModel(apiClient: APIClient()) class MyViewModel { let apiClient: APIClientProtocol init(apiClient: APIClientProtocol) { self.apiClient = apiClient } } APIClientProtocol "CTUSBDUUZQF *OKFDUDPODSFUFUZQF

!ZPJDIJUHZ Try dependency injection with Swinject Register/resolve-style DI container like
dictionary

!ZPJDIJUHZ How to use Swinject container $POUBJOFS Register Resolve

!ZPJDIJUHZ Code example of registration $POUBJOFS Register import Swinject let
container = Container() container.register(MyViewModel.self) { resolver in let apiClient = resolver.resolve(APIClientProtocol.self)! return MyViewModel(apiClient: apiClient) } container.register(APIClientProtocol.self) { _ in APIClient() }

!ZPJDIJUHZ Code example of resolution $POUBJOFS Resolve import Swinject let
vm = container.resolve(MyViewModel.self)!

!ZPJDIJUHZ It’s ok for a simple case, but…

!ZPJDIJUHZ In a production app class MyViewModel { init(dep1: D1,
dep2: D2, dep3: D3, id: String, name: String) { ... } } .BOZEFQFOEFODJFT 3VOUJNFQBSBNFUFST PUIFSUIBOEFQFOEFODJFT %FQFOEFODZJOKFDUJPODPEFJTPGUFOMJLFUIJT

!ZPJDIJUHZ Using typealias of dependency tuple init(dependency: Dependency, id: String,
name: String) 5ZQFBMJBTPGUVQMF % % % %FQFOEFODZ 1BSBNFUFST

!ZPJDIJUHZ Example of class deﬁnition with typealias of tuple protocol
APIClientProtocol { ... } class APIClient: APIClientProtocol { ... } protocol LoggerProtocol { ... } class Logger: LoggerProtocol { ... } 5ZQFBMJBTPG EFQFOEFODZUVQMF class MyViewModel { typealias Dependency = ( APIClientProtocol, LoggerProtocol ) let (apiClient, logger): Dependency let id: String init(dependency: Dependency, id: String) { (apiClient, logger) = dependency self.id = id } } &YBNQMFXJUIEFQFOEFODJFTBOEQBSBNFUFS

!ZPJDIJUHZ DI Registration let container = Container() container.register(APIClientProtocol.self) { _
in APIClient() } container.register(LoggerProtocol.self) { _ in Logger() } $POUBJOFS Register container.register(MyViewModel.self) { (resolver, id: String) in let dependency = ( resolver.resolve(APIClientProtocol.self)!, resolver.resolve(LoggerProtocol.self)! ) return MyViewModel( dependency: dependency, id: id ) }

!ZPJDIJUHZ DI Resolution let myViewModel = container.resolve( MyViewModel.self, argument: "abc")!
$POUBJOFS Resolve

!ZPJDIJUHZ Good to evolve the system

!ZPJDIJUHZ Summary • Architecture is not static but dynamic to
evolve. • Dependency injection is sticky-like glue. • Use a typealias to group dependencies.

!ZPJDIJUHZ More info, thanks! • Swinject Tutorial for iOS: Getting
Started by Gemma Barlow at raywenderlich.com • iOS App Development: Design Patterns for Mobile Architecture by Jon Bott at lynda.com • Dependency injection in Swift by Manuel Munoz at blog.quadiontech.com • Adventures in Dependency Swinjection by Ben Dietzkis at medium.com/@topLayoutGuide • Swinject - Dependency Injection in iOS by Iron Ben Zvi at speakerdeck.com/oronbz

Practical Structure to Configure Dependency Inj...

Practical Structure to Configure Dependency Injection in Swift for iOS

More Decks by Yoichi Tagaya

Other Decks in Programming

Featured

Transcript