final class ExperiencesViewController: UIViewController {
  // We can't name this view since UIViewController has a view: UIView property.
  private lazy var _view = CustomView()

  loadView() {
    self.view = _view
  }
}

// WRONG
class UrlValidator {

  func isValidUrl(_ URL: URL) -> Bool {
    // ...
  }

  func isProfileUrl(_ URL: URL, for userId: String) -> Bool {
    // ...
  }
}

let URLValidator = UrlValidator()
let isProfile = URLValidator.isProfileUrl(URLToTest, userId: IDOfUser)

// RIGHT
class URLValidator {

  func isValidURL(_ url: URL) -> Bool {
    // ...
  }

  func isProfileURL(_ url: URL, for userID: String) -> Bool {
    // ...
  }
}

let urlValidator = URLValidator()
let isProfile = urlValidator.isProfileURL(urlToTest, userID: idOfUser)

// WRONG
let rightTitleMargin: CGFloat
let leftTitleMargin: CGFloat
let bodyRightMargin: CGFloat
let bodyLeftMargin: CGFloat

// RIGHT
let titleMarginRight: CGFloat
let titleMarginLeft: CGFloat
let bodyMarginRight: CGFloat
let bodyMarginLeft: CGFloat

// WRONG
let title: String
let cancel: UIButton

// RIGHT
let titleText: String
let cancelButton: UIButton

// WRONG
class ExperiencesViewController {

  private func handleBookButtonTap() {
    // ...
  }

  private func modelChanged() {
    // ...
  }
}

// RIGHT
class ExperiencesViewController {

  private func didTapBookButton() {
    // ...
  }

  private func modelDidChange() {
    // ...
  }
}

// WRONG
class AIRAccount {
  // ...
}

// RIGHT
class Account {
  // ...
}

Functions

• (link) Omit Void return types from function definitions.

  Void {
  …
  }

  // RIGHT
  func doSomething() {
  …
  }
  “>

  // WRONG
  func doSomething() -> Void {
    ...
  }
  
  // RIGHT
  func doSomething() {
    ...
  }

• (link) Separate long function declarations with line breaks before each argument label and before the return signature. Put the open curly brace on the next line so the first executable line doesn’t look like it’s another parameter.

  String {
  // This is too long and will probably auto-wrap in a weird way
  }

  // WRONG
  func generateStars(at location: Point,
  count: Int,
  color: StarColor,
  withAverageDistance averageDistance: Float) -> String
  {
  // Xcode indents all the arguments
  }

  // WRONG
  func generateStars(
  at location: Point,
  count: Int,
  color: StarColor,
  withAverageDistance averageDistance: Float) -> String {
  populateUniverse() // this line blends in with the argument list
  }

  // WRONG
  func generateStars(
  at location: Point,
  count: Int,
  color: StarColor,
  withAverageDistance averageDistance: Float) throws
  -> String {
  populateUniverse() // this line blends in with the argument list
  }

  // RIGHT
  func generateStars(
  at location: Point,
  count: Int,
  color: StarColor,
  withAverageDistance averageDistance: Float)
  -> String
  {
  populateUniverse()
  }

  // RIGHT
  func generateStars(
  at location: Point,
  count: Int,
  color: StarColor,
  withAverageDistance averageDistance: Float)
  throws -> String
  {
  populateUniverse()
  }
  }
  “>

  class Universe {
  
    // WRONG
    func generateStars(at location: Point, count: Int, color: StarColor, withAverageDistance averageDistance: Float) -> String {
      // This is too long and will probably auto-wrap in a weird way
    }
  
    // WRONG
    func generateStars(at location: Point,
                       count: Int,
                       color: StarColor,
                       withAverageDistance averageDistance: Float) -> String
    {
      // Xcode indents all the arguments
    }
  
    // WRONG
    func generateStars(
      at location: Point,
      count: Int,
      color: StarColor,
      withAverageDistance averageDistance: Float) -> String {
      populateUniverse() // this line blends in with the argument list
    }
  
    // WRONG
    func generateStars(
      at location: Point,
      count: Int,
      color: StarColor,
      withAverageDistance averageDistance: Float) throws
      -> String {
      populateUniverse() // this line blends in with the argument list
    }
  
    // RIGHT
    func generateStars(
      at location: Point,
      count: Int,
      color: StarColor,
      withAverageDistance averageDistance: Float)
      -> String
    {
      populateUniverse()
    }
  
    // RIGHT
    func generateStars(
      at location: Point,
      count: Int,
      color: StarColor,
      withAverageDistance averageDistance: Float)
      throws -> String
    {
      populateUniverse()
    }
  }

• (link) Long function invocations should also break on each argument. Put the closing parenthesis on the last line of the invocation.

  // WRONG
  universe.generateStars(at: location, count: 5, color: starColor, withAverageDistance: 4)
  
  // WRONG
  universe.generateStars(at: location,
                         count: 5,
                         color: starColor,
                         withAverageDistance: 4)
  
  // WRONG
  universe.generateStars(
    at: location,
    count: 5,
    color: starColor,
    withAverageDistance: 4
  )
  
  // WRONG
  universe.generate(5,
    .stars,
    at: location)
  
  // RIGHT
  universe.generateStars(
    at: location,
    count: 5,
    color: starColor,
    withAverageDistance: 4)
  
  // RIGHT
  universe.generate(
    5,
    .stars,
    at: location)

Closures

• (link) Favor Void return types over () in closure declarations. If you must specify a Void return type in a function declaration, use Void rather than () to improve readability.

  ()) {
  …
  }

  // RIGHT
  func method(completion: () -> Void) {
  …
  }
  “>

  // WRONG
  func method(completion: () -> ()) {
    ...
  }
  
  // RIGHT
  func method(completion: () -> Void) {
    ...
  }

• (link) Name unused closure parameters as underscores (_).

  Why?

  Naming unused closure parameters as underscores reduces the cognitive overhead required to read closures by making it obvious which parameters are used and which are unused.

  // WRONG
  someAsyncThing() { argument1, argument2, argument3 in
    print(argument3)
  }
  
  // RIGHT
  someAsyncThing() { _, _, argument3 in
    print(argument3)
  }

• (link) Single-line closures should have a space inside each brace.

  // WRONG
  let evenSquares = numbers.filter {$0 % 2 == 0}.map {  $0 * $0  }
  
  // RIGHT
  let evenSquares = numbers.filter { $0 % 2 == 0 }.map { $0 * $0 }

Operators

• (link) Infix operators should have a single space on either side. Prefer parenthesis to visually group statements with many operators rather than varying widths of whitespace. This rule does not apply to range operators (e.g. 1...3) and postfix or prefix operators (e.g. guest? or -1).

  // WRONG
  let capacity = 1+2
  let capacity = currentCapacity   ?? 0
  let mask = (UIAccessibilityTraitButton|UIAccessibilityTraitSelected)
  let capacity=newCapacity
  let latitude = region.center.latitude - region.span.latitudeDelta/2.0
  
  // RIGHT
  let capacity = 1 + 2
  let capacity = currentCapacity ?? 0
  let mask = (UIAccessibilityTraitButton | UIAccessibilityTraitSelected)
  let capacity = newCapacity
  let latitude = region.center.latitude - (region.span.latitudeDelta / 2.0)

⬆
back to top

Patterns

• (link) Prefer initializing properties at init time whenever possible, rather than using implicitly unwrapped optionals. A notable exception is UIViewController’s view property.

  // WRONG
  class MyClass {
  
    init() {
      super.init()
      someValue = 5
    }
  
    var someValue: Int!
  }
  
  // RIGHT
  class MyClass {
  
    init() {
      someValue = 0
      super.init()
    }
  
    var someValue: Int
  }

• (link) Avoid performing any meaningful or time-intensive work in init(). Avoid doing things like opening database connections, making network requests, reading large amounts of data from disk, etc. Create something like a start() method if these things need to be done before an object is ready for use.

• (link) Extract complex property observers into methods. This reduces nestedness, separates side-effects from property declarations, and makes the usage of implicitly-passed parameters like oldValue explicit.

  // WRONG
  class TextField {
    var text: String? {
      didSet {
        guard oldValue != text else {
          return
        }
  
        // Do a bunch of text-related side-effects.
      }
    }
  }
  
  // RIGHT
  class TextField {
    var text: String? {
      didSet { textDidUpdate(from: oldValue) }
    }
  
    private func textDidUpdate(from oldValue: String?) {
      guard oldValue != text else {
        return
      }
  
      // Do a bunch of text-related side-effects.
    }
  }

• (link) Extract complex callback blocks into methods. This limits the complexity introduced by weak-self in blocks and reduces nestedness. If you need to reference self in the method call, make use of guard to unwrap self for the duration of the callback.

  Void) {
  API.request() { [weak self] response in
  if let self = self {
  // Processing and side effects
  }
  completion()
  }
  }
  }

  // RIGHT
  class MyClass {

  func request(completion: () -> Void) {
  API.request() { [weak self] response in
  guard let self = self else { return }
  self.doSomething(with: self.property, response: response)
  completion()
  }
  }

  func doSomething(with nonOptionalParameter: SomeClass, response: SomeResponseClass) {
  // Processing and side effects
  }
  }
  “>

  //WRONG
  class MyClass {
  
    func request(completion: () -> Void) {
      API.request() { [weak self] response in
        if let self = self {
          // Processing and side effects
        }
        completion()
      }
    }
  }
  
  // RIGHT
  class MyClass {
  
    func request(completion: () -> Void) {
      API.request() { [weak self] response in
        guard let self = self else { return }
        self.doSomething(with: self.property, response: response)
        completion()
      }
    }
  
    func doSomething(with nonOptionalParameter: SomeClass, response: SomeResponseClass) {
      // Processing and side effects
    }
  }

• (link) Prefer using guard at the beginning of a scope.

  Why?

  It’s easier to reason about a block of code when all guard statements are grouped together at the top rather than intermixed with business logic.

• (link) Access control should be at the strictest level possible. Prefer public to open and private to fileprivate unless you need that behavior.

• (link) Avoid global functions whenever possible. Prefer methods within type definitions.

  Int {
  // …
  }

  func jump(person: Person) {
  // …
  }

  // RIGHT
  class Person {
  var bornAt: TimeInterval

  var age: Int {
  // …
  }

  func jump() {
  // …
  }
  }
  “>

  // WRONG
  func age(of person, bornAt timeInterval) -> Int {
    // ...
  }
  
  func jump(person: Person) {
    // ...
  }
  
  // RIGHT
  class Person {
    var bornAt: TimeInterval
  
    var age: Int {
      // ...
    }
  
    func jump() {
      // ...
    }
  }

• (link) Use caseless enums for organizing public or internal constants and functions into namespaces.

  • Avoid creating non-namespaced global constants and functions.
  • Feel free to nest namespaces where it adds clarity.
  • private globals are permitted, since they are scoped to a single file and do not pollute the global namespace. Consider placing private globals in an enum namespace to match the guidelines for other declaration types.

  Why?

  Caseless enums work well as namespaces because they cannot be instantiated, which matches their intent.

  enum Environment {
  
    enum Earth {
      static let gravity = 9.8
    }
  
    enum Moon {
      static let gravity = 1.6
    }
  }

• (link) Use Swift’s automatic enum values unless they map to an external source. Add a comment explaining why explicit values are defined.

  Why?

  To minimize user error, improve readability, and write code faster, rely on Swift’s automatic enum values. If the value maps to an external source (e.g. it’s coming from a network request) or is persisted across binaries, however, define the values explicity, and document what these values are mapping to.

  This ensures that if someone adds a new value in the middle, they won’t accidentally break things.

  // WRONG
  enum ErrorType: String {
    case error = "error"
    case warning = "warning"
  }
  
  enum UserType: String {
    case owner
    case manager
    case member
  }
  
  enum Planet: Int {
    case mercury = 0
    case venus = 1
    case earth = 2
    case mars = 3
    case jupiter = 4
    case saturn = 5
    case uranus = 6
    case neptune = 7
  }
  
  enum ErrorCode: Int {
    case notEnoughMemory
    case invalidResource
    case timeOut
  }
  
  // RIGHT
  enum ErrorType: String {
    case error
    case warning
  }
  
  /// These are written to a logging service. Explicit values ensure they're consistent across binaries.
  // swiftlint:disable redundant_string_enum_value
  enum UserType: String {
    case owner = "owner"
    case manager = "manager"
    case member = "member"
  }
  // swiftlint:enable redundant_string_enum_value
  
  enum Planet: Int {
    case mercury
    case venus
    case earth
    case mars
    case jupiter
    case saturn
    case uranus
    case neptune
  }
  
  /// These values come from the server, so we set them here explicitly to match those values.
  enum ErrorCode: Int {
    case notEnoughMemory = 0
    case invalidResource = 1
    case timeOut = 2
  }

• (link) Use optionals only when they have semantic meaning.

• (link) Prefer immutable values whenever possible. Use map and compactMap instead of appending to a new collection. Use filter instead of removing elements from a mutable collection.

  Why?

  Mutable variables increase complexity, so try to keep them in as narrow a scope as possible.

  // WRONG
  var results = [SomeType]()
  for element in input {
    let result = transform(element)
    results.append(result)
  }
  
  // RIGHT
  let results = input.map { transform($0) }

  // WRONG
  var results = [SomeType]()
  for element in input {
    if let result = transformThatReturnsAnOptional(element) {
      results.append(result)
    }
  }
  
  // RIGHT
  let results = input.compactMap { transformThatReturnsAnOptional($0) }

• (link) Prefer immutable or computed static properties over mutable ones whenever possible. Use stored static let properties or computed static var properties over stored static vars properties whenever possible, as stored static var properties are global mutable state.

  Why?

  Global mutable state increases complexity and makes it harder to reason about the behavior of applications. It should be avoided when possible.

  // WRONG
  enum Fonts {
    static var title = UIFont(…)
  }
  
  // RIGHT
  enum Fonts {
    static let title = UIFont(…)
  }

  // WRONG
  struct FeatureState {
    var count: Int
  
    static var initial = FeatureState(count: 0)
  }
  
  // RIGHT
  struct FeatureState {
    var count: Int
  
    static var initial: FeatureState {
      // Vend static properties that are cheap to compute
      FeatureState(count: 0)
    }
  }

• (link) Handle an unexpected but recoverable condition with an assert method combined with the appropriate logging in production. If the unexpected condition is not recoverable, prefer a precondition method or fatalError(). This strikes a balance between crashing and providing insight into unexpected conditions in the wild. Only prefer fatalError over a precondition method when the failure message is dynamic, since a precondition method won’t report the message in the crash report.

  Item {
  precondition(index >= 0 && index UIImage {
  guard let image = UIImage(named: name, in: nil, compatibleWith: nil) else {
  fatalError("Image named \(name) couldn’t be loaded.")
  // We want the error message so we know the name of the missing image.
  }
  return image
  }
  “>

  func didSubmitText(_ text: String) {
    // It's unclear how this was called with an empty string; our custom text field shouldn't allow this.
    // This assert is useful for debugging but it's OK if we simply ignore this scenario in production.
    guard !text.isEmpty else {
      assertionFailure("Unexpected empty string")
      return
    }
    // ...
  }
  
  func transformedItem(atIndex index: Int, from items: [Item]) -> Item {
    precondition(index >= 0 && index < items.count)
    // It's impossible to continue executing if the precondition has failed.
    // ...
  }
  
  func makeImage(name: String) -> UIImage {
    guard let image = UIImage(named: name, in: nil, compatibleWith: nil) else {
      fatalError("Image named \(name) couldn't be loaded.")
      // We want the error message so we know the name of the missing image.
    }
    return image
  }

• (link) Default type methods to static.

  Why?

  If a method needs to be overridden, the author should opt into that functionality by using the class keyword instead.

  // WRONG
  class Fruit {
    class func eatFruits(_ fruits: [Fruit]) { ... }
  }
  
  // RIGHT
  class Fruit {
    static func eatFruits(_ fruits: [Fruit]) { ... }
  }

• (link) Default classes to final.

  Why?

  If a class needs to be overridden, the author should opt into that functionality by omitting the final keyword.

  // WRONG
  class SettingsRepository {
    // ...
  }
  
  // RIGHT
  final class SettingsRepository {
    // ...
  }

• (link) Never use the default case when switching over an enum.

  Why?

  Enumerating every case requires developers and reviewers have to consider the correctness of every switch statement when new cases are added.

  // WRONG
  switch anEnum {
  case .a:
    // Do something
  default:
    // Do something else.
  }
  
  // RIGHT
  switch anEnum {
  case .a:
    // Do something
  case .b, .c:
    // Do something else.
  }

• (link) Check for nil rather than using optional binding if you don’t need to use the value.

  Why?

  Checking for nil makes it immediately clear what the intent of the statement is. Optional binding is less explicit.

  var thing: Thing?
  
  // WRONG
  if let _ = thing {
    doThing()
  }
  
  // RIGHT
  if thing != nil {
    doThing()
  }

• (link) Omit the return keyword when not required by the language.

  UIAlertController {
  return UIAlertController(
  title: "ℹ️ Info",
  message: message,
  preferredStyle: .alert)
  }

  // RIGHT
  ["1", "2", "3"].compactMap { Int($0) }

  var size: CGSize {
  CGSize(
  width: 100.0,
  height: 100.0)
  }

  func makeInfoAlert(message: String) -> UIAlertController {
  UIAlertController(
  title: "ℹ️ Info",
  message: message,
  preferredStyle: .alert)
  }
  “>

  // WRONG
  ["1", "2", "3"].compactMap { return Int($0) }
  
  var size: CGSize {
    return CGSize(
      width: 100.0,
      height: 100.0)
  }
  
  func makeInfoAlert(message: String) -> UIAlertController {
    return UIAlertController(
      title: "ℹ️ Info",
      message: message,
      preferredStyle: .alert)
  }
  
  // RIGHT
  ["1", "2", "3"].compactMap { Int($0) }
  
  var size: CGSize {
    CGSize(
      width: 100.0,
      height: 100.0)
  }
  
  func makeInfoAlert(message: String) -> UIAlertController {
    UIAlertController(
      title: "ℹ️ Info",
      message: message,
      preferredStyle: .alert)
  }

• (link) Use AnyObject instead of class in protocol definitions.

  Why?

  SE-0156, which introduced support for using the AnyObject keyword as a protocol constraint, recommends preferring AnyObject over class:

  This proposal merges the concepts of class and AnyObject, which now have the same meaning: they represent an existential for classes. To get rid of the duplication, we suggest only keeping AnyObject around. To reduce source-breakage to a minimum, class could be redefined as typealias class = AnyObject and give a deprecation warning on class for the first version of Swift this proposal is implemented in. Later, class could be removed in a subsequent version of Swift.

  // WRONG
  protocol Foo: class {}
  
  // RIGHT
  protocol Foo: AnyObject {}

• (link) Specify the access control for each declaration in an extension individually.

  Why?

  Specifying the access control on the declaration itself helps engineers more quickly determine the access control level of an individual declaration.

  // WRONG
  public extension Universe {
    // This declaration doesn't have an explicit access control level.
    // In all other scopes, this would be an internal function,
    // but because this is in a public extension, it's actually a public function.
    func generateGalaxy() { }
  }
  
  // WRONG
  private extension Spaceship {
    func enableHyperdrive() { }
  }
  
  // RIGHT
  extension Universe {
    // It is immediately obvious that this is a public function,
    // even if the start of the `extension Universe` scope is off-screen.
    public func generateGalaxy() { }
  }
  
  // RIGHT
  extension Spaceship {
    // Recall that a private extension actually has fileprivate semantics,
    // so a declaration in a private extension is fileprivate by default.
    fileprivate func enableHyperdrive() { }
  }

• (link) Prefer dedicated logging systems like os_log or swift-log over writing directly to standard out using print(…), debugPrint(…), or dump(…).

  Why?

  All log messages should flow into intermediate logging systems that can direct messages to the correct destination(s) and potentially filter messages based on the app’s environment or configuration. print(…), debugPrint(…), or dump(…) will write all messages directly to standard out in all app configurations and can potentially leak personally identifiable information (PII).

⬆
back to top

File Organization

• (link) Alphabetize and deduplicate module imports within a file. Place all imports at the top of the file below the header comments. Do not add additional line breaks between import statements. Add a single empty line before the first import and after the last import.

  Why?

  • A standard organization method helps engineers more quickly determine which modules a file depends on.
  • Duplicated import statements have no effect and should be removed for clarity.

  // WRONG
  
  //  Copyright © 2018 Airbnb. All rights reserved.
  //
  import DLSPrimitives
  import Constellation
  import Constellation
  import Epoxy
  
  import Foundation
  
  //RIGHT
  
  //  Copyright © 2018 Airbnb. All rights reserved.
  //
  
  import Constellation
  import DLSPrimitives
  import Epoxy
  import Foundation

  Exception: @testable import should be grouped after the regular import and separated by an empty line.

  // WRONG
  
  //  Copyright © 2018 Airbnb. All rights reserved.
  //
  
  import DLSPrimitives
  @testable import Epoxy
  import Foundation
  import Nimble
  import Quick
  
  //RIGHT
  
  //  Copyright © 2018 Airbnb. All rights reserved.
  //
  
  import DLSPrimitives
  import Foundation
  import Nimble
  import Quick
  
  @testable import Epoxy

• (link) Limit consecutive whitespace to one blank line or space (excluding indentation). Favor the following formatting guidelines over whitespace of varying heights or widths.

  // WRONG
  struct Planet {
  
    let mass:          Double
    let hasAtmosphere: Bool
  
  
    func distance(to: Planet) { }
  
  }
  
  // RIGHT
  struct Planet {
  
    let mass: Double
    let hasAtmosphere: Bool
  
    func distance(to: Planet) { }
  
  }

• (link) Files should end in a newline.

• (link) Each type and extension which implements a conformance should be preceded by a MARK comment.

  • Types should be preceded by a // MARK: - TypeName comment.
  • Extensions that add a conformance should be preceded by a // MARK: - TypeName + ProtocolName comment.
  • Extensions that immediately follow the type being extended should omit that type’s name and instead use // MARK: ProtocolName.
  • If there is only one type or extension in a file, the MARK comment can be omitted.
  • If the extension in question is empty (e.g. has no declarations in its body), the MARK comment can be omitted.
  • For extensions that do not add new conformances, consider adding a MARK with a descriptive comment.

  // MARK: - GalaxyView
  
  final class GalaxyView: UIView { … }
  
  // MARK: ContentConfigurableView
  
  extension GalaxyView: ContentConfigurableView { … }
  
  // MARK: - Galaxy + SpaceThing, NamedObject
  
  extension Galaxy: SpaceThing, NamedObject { … }

• (link) Use // MARK: to separate the contents of type definitions and extensions into the sections listed below, in order. All type definitions and extensions should be divided up in this consistent way, allowing a reader of your code to easily jump to what they are interested in.

  • // MARK: Lifecycle for init and deinit methods.
  • // MARK: Open for open properties and methods.
  • // MARK: Public for public properties and methods.
  • // MARK: Internal for internal properties and methods.
  • // MARK: Fileprivate for fileprivate properties and methods.
  • // MARK: Private for private properties and methods.
  • If the type in question is an enum, its cases should go above the first // MARK:.
  • Do not subdivide each of these sections into subsections, as it makes the method dropdown more cluttered and therefore less useful. Instead, group methods by functionality and use smart naming to make clear which methods are related. If there are enough methods that sub-sections seem necessary, consider refactoring your code into multiple types.
  • If all of the type or extension’s definitions belong to the same category (e.g. the type or extension only consists of internal properties), it is OK to omit the // MARK:s.
  • If the type in question is a simple value type (e.g. fewer than 20 lines), it is OK to omit the // MARK:s, as it would hurt legibility.

• (link) Within each top-level section, place content in the following order. This allows a new reader of your code to more easily find what they are looking for.

  • Nested types and typealiases
  • Static properties
  • Class properties
  • Instance properties
  • Static methods
  • Class methods
  • Instance methods

• (link) Add empty lines between property declarations of different kinds. (e.g. between static properties and instance properties.)

  // WRONG
  static let gravityEarth: CGFloat = 9.8
  static let gravityMoon: CGFloat = 1.6
  var gravity: CGFloat
  
  // RIGHT
  static let gravityEarth: CGFloat = 9.8
  static let gravityMoon: CGFloat = 1.6
  
  var gravity: CGFloat

• (link) Computed properties and properties with property observers should appear at the end of the set of declarations of the same kind. (e.g. instance properties.)

  // WRONG
  var atmosphere: Atmosphere {
    didSet {
      print("oh my god, the atmosphere changed")
    }
  }
  var gravity: CGFloat
  
  // RIGHT
  var gravity: CGFloat
  var atmosphere: Atmosphere {
    didSet {
      print("oh my god, the atmosphere changed")
    }
  }

⬆
back to top

Objective-C Interoperability

• (link) Prefer pure Swift classes over subclasses of NSObject. If your code needs to be used by some Objective-C code, wrap it to expose the desired functionality. Use @objc on individual methods and variables as necessary rather than exposing all API on a class to Objective-C via @objcMembers.

  class PriceBreakdownViewController {
  
    private let acceptButton = UIButton()
  
    private func setUpAcceptButton() {
      acceptButton.addTarget(
        self,
        action: #selector(didTapAcceptButton),
        forControlEvents: .touchUpInside)
    }
  
    @objc
    private func didTapAcceptButton() {
      // ...
    }
  }

⬆
back to top

Contributors

• View Contributors

⬆
back to top

Amendments

We encourage you to fork this guide and change the rules to fit your team’s style guide. Below, you may list some amendments to the style guide. This allows you to periodically update your style guide without having to deal with merge conflicts.

⬆
back to top

GitHub

https://github.com/airbnb/swift