Застосування: Патерн можна часто зустріти в Swift-коді, особливо там, де потрібна конвертація різних типів даних або спільна робота класів з різними інтерфейсами.
Ознаки застосування патерна: Адаптер отримує конвертований об’єкт у конструкторі або через параметри своїх методів. Методи Адаптера, зазвичай, сумісні з інтерфейсом одного об’єкта. Вони делегують виклики вкладеному об’єктові, перетворивши перед цим параметри виклику у формат, підтримуваний вкладеним об’єктом.
Цей приклад показує структуру патерна Адаптер, а саме — з яких класів він складається, які ролі ці класи виконують і як вони взаємодіють один з одним.
Після ознайомлення зі структурою, вам буде легше сприймати наступний приклад, що розглядає реальний випадок використання патерна в світі Swift.
Example.swift: Приклад структури патерна
import XCTest /// The Target defines the domain-specific interface used by the client code. class Target { func request() -> String { return "Target: The default target's behavior." } } /// The Adaptee contains some useful behavior, but its interface is incompatible /// with the existing client code. The Adaptee needs some adaptation before the /// client code can use it. class Adaptee { public func specificRequest() -> String { return ".eetpadA eht fo roivaheb laicepS" } } /// The Adapter makes the Adaptee's interface compatible with the Target's /// interface. class Adapter: Target { private var adaptee: Adaptee init(_ adaptee: Adaptee) { self.adaptee = adaptee } override func request() -> String { return "Adapter: (TRANSLATED) " + adaptee.specificRequest().reversed() } } /// The client code supports all classes that follow the Target interface. class Client { // ... static func someClientCode(target: Target) { print(target.request()) } // ... } /// Let's see how it all works together. class AdapterConceptual: XCTestCase { func testAdapterConceptual() { print("Client: I can work just fine with the Target objects:") Client.someClientCode(target: Target()) let adaptee = Adaptee() print("Client: The Adaptee class has a weird interface. See, I don't understand it:") print("Adaptee: " + adaptee.specificRequest()) print("Client: But I can work with it via the Adapter:") Client.someClientCode(target: Adapter(adaptee)) } }
Output.txt: Результат виконання
Client: I can work just fine with the Target objects: Target: The default target's behavior. Client: The Adaptee class has a weird interface. See, I don't understand it: Adaptee: .eetpadA eht fo roivaheb laicepS Client: But I can work with it via the Adapter: Adapter: (TRANSLATED) Special behavior of the Adaptee.
Життєвий приклад
Example.swift: Життєвий приклад
import XCTest import UIKit /// Adapter Design Pattern /// /// Intent: Convert the interface of a class into the interface clients expect. /// Adapter lets classes work together that couldn't work otherwise because of /// incompatible interfaces. class AdapterRealWorld: XCTestCase { /// Example. Let's assume that our app perfectly works with Facebook /// authorization. However, users ask you to add sign in via Twitter. /// /// Unfortunately, Twitter SDK has a different authorization method. /// /// Firstly, you have to create the new protocol 'AuthService' and insert /// the authorization method of Facebook SDK. /// /// Secondly, write an extension for Twitter SDK and implement methods of /// AuthService protocol, just a simple redirect. /// /// Thirdly, write an extension for Facebook SDK. You should not write any /// code at this point as methods already implemented by Facebook SDK. /// /// It just tells a compiler that both SDKs have the same interface. func testAdapterRealWorld() { print("Starting an authorization via Facebook") startAuthorization(with: FacebookAuthSDK()) print("Starting an authorization via Twitter.") startAuthorization(with: TwitterAuthSDK()) } func startAuthorization(with service: AuthService) { /// The current top view controller of the app let topViewController = UIViewController() service.presentAuthFlow(from: topViewController) } } protocol AuthService { func presentAuthFlow(from viewController: UIViewController) } class FacebookAuthSDK { func presentAuthFlow(from viewController: UIViewController) { /// Call SDK methods and pass a view controller print("Facebook WebView has been shown.") } } class TwitterAuthSDK { func startAuthorization(with viewController: UIViewController) { /// Call SDK methods and pass a view controller print("Twitter WebView has been shown. Users will be happy :)") } } extension TwitterAuthSDK: AuthService { /// This is an adapter /// /// Yeah, we are able to not create another class and just extend an /// existing one func presentAuthFlow(from viewController: UIViewController) { print("The Adapter is called! Redirecting to the original method...") self.startAuthorization(with: viewController) } } extension FacebookAuthSDK: AuthService { /// This extension just tells a compiler that both SDKs have the same /// interface. }
Output.txt: Результат виконання
Starting an authorization via Facebook Facebook WebView has been shown /// Starting an authorization via Twitter The Adapter is called! Redirecting to the original method... Twitter WebView has been shown. Users will be happy :)
