2e1bfa4 Jul 19, 2018
3 contributors

Users who have contributed to this file

@kzaher @Vkt0r @freak4pc
51 lines (41 sloc) 1.57 KB


  • Always strive to model your systems or their parts as pure functions. Those pure functions can be tested easily and can be used to modify operator behaviors.
  • When you are using Rx, first try to compose built-in operators.
  • If using some combination of operators often, create your convenience operators.


extension ObservableType where E: MaybeCool {

    public func coolElements()
        -> Observable<E> {
          return filter { e -> Bool in
              return e.isCool
  • Rx operators are as general as possible, but there will always be edge cases that will be hard to model. In those cases you can just create your own operator and possibly use one of the built-in operators as a reference.

  • Always use operators to compose subscriptions.

Avoid nesting subscribe calls at all cost. This is a code smell.

textField.rx.text.subscribe(onNext: { text in
    performURLRequest(text).subscribe(onNext: { result in
    .disposed(by: disposeBag)
.disposed(by: disposeBag)

Preferred way of chaining disposables by using operators.

    .flatMapLatest { text in
        // Assuming this doesn't fail and returns result on main scheduler,
        // otherwise `catchError` and `observeOn(MainScheduler.instance)` can be used to
        // correct this.
        return performURLRequest(text)
    .disposed(by: disposeBag) // only one top most disposable