jeamesbone

// First we need a scene for our ViewController
struct LandingScene: Scene {
    // Non optional, safe references to our vc's dependencies
    let client: APIClient
    let account: Account

    // Note the parameter type is the specific view controller we want to configure
    // This takes advantage of the `associatedtype` we defined in our protocol
    func configureViewController(_ viewController: LandingViewController) {
        // Inject the dependencies

jeamesbone

extension UIStoryboard {
    func instantiateViewController<S: Scene>(for scene: S) -> S.ViewController {
        guard let viewController = instantiateViewController(withIdentifier: scene.identifier) as? S.ViewController
        else {
                fatalError("expected view controller with identifier '\(scene.identifier)' to be of type '\(String(describing: S.ViewController.self))'")
        }
        scene.configureViewController(viewController)
        return viewController
    }
}

jeamesbone

extension Scene {
    var identifier: String {
        return String(describing: ViewController.self)
    }
}

jeamesbone

protocol Scene {
    associatedtype ViewController

    var identifier: String { get }

    func configureViewController(_ viewController: ViewController)
}

jeamesbone

// Value types are awesome, but we lose the ability to inherit functionality if we use structs in swift.
//
// Below are some experiments where I've been playing with composition to solve this for a common use case
//   where we want to have some common base model fields. 

import Foundation

// Create a struct to hold our common fields
struct CommonFields {
  let id: Int

jeamesbone

//  Copyright (c) 2015 Jeames Bone. All rights reserved.

import UIKit

extension UITableView {
    func animate(animations: () -> Void) {
        beginUpdates()
        animations()
        endUpdates()
    }