In most cases you’ll end up with all kinds of different methods handling these cases, but over time it can start to become unclear where to look when something needs to be changed or added inside your View Controller.

When a (new) team member has to work in the codebase that he has never touched before, it can take some time to find his/her way and know where to look. So how do I try to streamline this?

Swift Enums, your best friend.

Every interaction on the screen, triggers something, and I model all these interactions in a Swift enum called PerformAction .

The enum for the TravelPlanner screen looks like this:

Implementation

This enum is added as a nested type inside the TravelPlannerViewController, so you can reuse the same PerformAction enum name across your files without getting name collisions.

If a new member starts reading through your codebase, he/she can check this enum and see at a glance what all the different actions are for this screen.

To react on these interactions, we create a property performedActionand add a didSet property observer.

Swift

var actionPerformed:PerformAction = .nothing { didSet { switch actionPerformed { case .fromLocationRowPressed( let location ): presentLocationPicker( location: location ) case .toLocationRowPressed( let location ): presentLocationPicker( location: location ) case .switchLocationButtonPressed: switchLocations() case .departureArrivalRowPressed( let queryType, let date ): presentDatePicker( queryType, date: date ) ... } } }

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22

var actionPerformed:PerformAction = .nothing {       didSet {                  switch actionPerformed {                      case .fromLocationRowPressed( let location ):             presentLocationPicker( location: location )         case .toLocationRowPressed( let location ):             presentLocationPicker( location: location )         case .switchLocationButtonPressed:             switchLocations()         case .departureArrivalRowPressed( let queryType, let date ):             presentDatePicker( queryType, date: date )                  ...                      }              }   }

Proxying

Now you have 1 point of entry to handle all your interactions and call your methods.

Swift

@IBAction func fromLocationPressed( _ sender: UIButton ) { actionPerformed = .fromLocationRowPressed( location: fromLocationRow.location ) } @IBAction func switchButtonPressed( _ sender: UIButton ) { actionPerformed = .switchLocationButtonPressed }

1 2 3 4 5 6 7 8 9 10 11

@IBAction func fromLocationPressed( _ sender: UIButton ) {        actionPerformed = .fromLocationRowPressed( location: fromLocationRow.location )      }   @IBAction func switchButtonPressed( _ sender: UIButton ) {        actionPerformed = .switchLocationButtonPressed      }

When using RxSwift I use a PublishSubject to keep track of changes.

Swift

// Create the subject to keep track of the performed actions private let performedActionSubject = PublishSubject<PerformedAction>() // Add a new action to the stream performActionSubject.onNext( .travelOptionsButtonPressed ) // Get updates when an action has been performed viewModel.outputs.actionPerformedObservable.subscribe(onNext: { [weak self] (performedAction) in switch performedAction { case ... } }).disposed( by: disposeBag )

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

// Create the subject to keep track of the performed actions private let performedActionSubject = PublishSubject<PerformedAction>()      // Add a new action to the stream performActionSubject.onNext( .travelOptionsButtonPressed )      // Get updates when an action has been performed viewModel.outputs.actionPerformedObservable.subscribe(onNext: { [weak self] (performedAction) in          switch performedAction {              case ...          }   }).disposed( by: disposeBag )

Final thoughts

This is not a technique I use for a screen with only one or two actions. I tend to model it like this, if there are a lot of interactions.

The downside is you’ll get a bit of extra code, because you proxy your interaction handling to the PerformAction enum.

The benefits are

1. See all the interactions in the enum at a glance
2. Clarity of having one point where all the interactions are handled

For newcomers (or your future-you) it will be easier to get around the code.