Swiftpack.co - bigMOTOR/DataDrivenRxDatasources as Swift Package

Swiftpack.co is a collection of thousands of indexed Swift packages. Search packages.
See all packages published by bigMOTOR.
bigMOTOR/DataDrivenRxDatasources 3.5.2
DataDrivenRxDatasources - MVVM abstraction boilerplate code over RxDataSources.
⭐️ 14
🕓 3 weeks ago
.package(url: "https://github.com/bigMOTOR/DataDrivenRxDatasources.git", from: "3.5.2")


DataDrivenRxDatasources - MVVM abstraction boilerplate code over RxDataSources.

The standard approach to managing table/collection views with data sources has several flaws:

  • Repeated boilerplate code - data source and delegate methods, cell registration, etc.
  • Tangled follow the flow of control of TableView/CollectionView data source and delegate methods since they are often placed in a different order, far from each other, or even located in different files.
  • Violation of dependency inversion principle. The knowledge about which cells are attached to a table/collection view and how these cells are instantiated (nib or class) leaks to corresponding view controllers. View controller becomes dependent on the module of the lower level (table/collection view cell).
  • Leaves lots of room for mistakes, since data source methods must be consistent with each other. For example, if numberOfRows(inSection:), numberOfSections(in:) and tableView(_,cellForRowAt:) are inconsistent, it results in an unwanted behaviour or even crash. Cells in these methods is a generic UITableViewCell/UICollectionViewCell type which usually should be type casted to a concrete class.
  • Table/collection view data source protocol implementation is imperative and does not feel Swift way.

RxDataSources helps us to solve some of this problem with an elegant data binding mechanism and powerful AnimatableSectionModel & SectionModel abstractions, but still stays us on our own with repeatable cell registration and violation of dependency inversion principle.

DataDrivenRxDatasources brings another level of the abstractions and lets us address these issues and design a data-driven, reusable, declarative table/collection view components which depends only on its ViewModel. The core of our library is based on abstracted protocols that are supposed to provide binding sections and cells but don’t care what these sections and cells really are. More info on Medium

Installation DataDrivenRxDatasources available via:

Getting Started

private typealias SectionViewModel = AnimatableTableSectionModel<String>

let cellItems = [
      SampleCellViewModel(name: "Name 1"),
      SampleCellViewModel(name: "Name 2")
let sections: Driver<[AnimatableTableSectionModel<String>]> = .just([SectionViewModel(model: "Some Section", items: cellItems)])
  .bind(sections: sections)
  .disposed(by: bag)

Please take a look at our ‘Example’ project to get more use cases.


Dmytro Makarenko

Nikolay Fiantsev

Misha Markin

Dmytro Dovhan


  • Something wrong or you need anything else? Please open an issue or make a Pull Request.
  • Pull requests are welcome.


DataDrivenRxDatasources requires iOS11, RxDataSources 5.x and RxSwift 6.x. For the last iOS10 support, please use DataDrivenRxDatasources 2.1.0. For the last RxSwift 5.x support, please use DataDrivenRxDatasources 1.2.0.


DataDrivenRxDatasources is available under the MIT license. See the LICENSE file for more info.


Stars: 14
Last commit: 3 weeks ago
Advertisement: IndiePitcher.com - Cold Email Software for Startups

Release Notes

Decoratable TableView
3 weeks ago

What's Changed

Full Changelog: https://github.com/bigMOTOR/DataDrivenRxDatasources/compare/3.5.1...3.5.2

Swiftpack is being maintained by Petr Pavlik | @ptrpavlik | @swiftpackco | API | Analytics