the algorithm has the assumption that all sections and items are unique so there is no ambiguity
in case there is ambiguity, fallbacks automagically on non animated refresh
it applies additional heuristics to send the least number of commands to sectioned view
even though the running time is linear, preferred number of sent commands is usually a lot less than linear
it is preferred (and possible) to cap the number of changes to some small number, and in case the number of changes grows towards linear, just do normal reload
Supports extending your item and section structures
just extend your item with IdentifiableType and Equatable, and your section with AnimatableSectionModelType
Supports all combinations of two level hierarchical animations for both sections and items
Section animations: Insert, Delete, Move
Item animations: Insert, Delete, Move, Reload (if old value is not equal to new value)
Configurable animation types for Insert, Reload and Delete (Automatic, Fade, …)
Example app
Randomized stress tests (example app)
Supports editing out of the box (example app)
Works with UITableView and UICollectionView
Why
Writing table and collection view data sources is tedious. There is a large number of delegate methods that need to be implemented for the simplest case possible.
RxSwift helps alleviate some of the burden with a simple data binding mechanism:
Turn your data into an Observable sequence
Bind the data to the tableView/collectionView using one of:
let data = Observable<[String]>.just(["first element", "second element", "third element"])
data.bind(to: tableView.rx.items(cellIdentifier: "Cell")) { index, model, cell in
cell.textLabel?.text = model
}
.disposed(by: disposeBag)
This works well with simple data sets but does not handle cases where you need to bind complex data sets with multiples sections, or when you need to perform animations when adding/modifying/deleting items.
These are precisely the use cases that RxDataSources helps solve.
With RxDataSources, it is super easy to just write
### Animated Data Sources
RxDataSources provides two special data source types that automatically take care of animating changes in the bound data source: `RxTableViewSectionedAnimatedDataSource` and `RxCollectionViewSectionedAnimatedDataSource`.
To use one of the two animated data sources, you must take a few extra steps on top of those outlined above:
- SectionOfCustomData needs to conform to `AnimatableSectionModelType`
- Your data model must conform to
* `IdentifiableType`: The `identity` provided by the `IdentifiableType` protocol must be an **immutable identifier representing an instance of the model**. For example, in case of a `Car` model, you might want to use the car's `plateNumber` as its identity.
* `Equatable`: Conforming to `Equatable` helps `RxDataSources` determine which cells have changed so it can animate only these specific cells. Meaning, changing **any** of the `Car` model's properties will trigger an animated reload of that cell.
## Requirements
Xcode 10.2
Swift 5.0
For Swift 4.x version please use versions `3.0.0 ... 3.1.0`
For Swift 3.x version please use versions `1.0 ... 2.0.2`
For Swift 2.3 version please use versions `0.1 ... 0.9`
## Installation
**We'll try to keep the API as stable as possible, but breaking API changes can occur.**
### CocoaPods
Podfile
pod ‘RxDataSources’, ‘~> 5.0’
### Carthage
Cartfile
github “RxSwiftCommunity/RxDataSources” ~> 5.0
### Swift Package Manager
Create a `Package.swift` file.
```swift
import PackageDescription
let package = Package(
name: "SampleProject",
dependencies: [
.package(url: "https://github.com/RxSwiftCommunity/RxDataSources.git", from: "5.0.0")
]
)
Table and Collection view data sources
Features
IdentifiableType
andEquatable
, and your section withAnimatableSectionModelType
Insert
,Reload
andDelete
(Automatic, Fade, …)UITableView
andUICollectionView
Why
Writing table and collection view data sources is tedious. There is a large number of delegate methods that need to be implemented for the simplest case possible.
RxSwift helps alleviate some of the burden with a simple data binding mechanism:
rx.items(dataSource:protocol<RxTableViewDataSourceType, UITableViewDataSource>)
rx.items(cellIdentifier:String)
rx.items(cellIdentifier:String:Cell.Type:_:)
rx.items(_:_:)
This works well with simple data sets but does not handle cases where you need to bind complex data sets with multiples sections, or when you need to perform animations when adding/modifying/deleting items.
These are precisely the use cases that RxDataSources helps solve.
With RxDataSources, it is super easy to just write
How
Given the following custom data structure:
SectionModelType
protocol:Item
typealias: equal to the type of items that the section will containitems
property: of type array ofItem
Create a dataSource object and pass it your
SectionOfCustomData
type:Customize closures on the dataSource as needed:
titleForHeaderInSection
titleForFooterInSection
Observable.just(sections) .bind(to: tableView.rx.items(dataSource: dataSource)) .disposed(by: disposeBag)
pod ‘RxDataSources’, ‘~> 5.0’
github “RxSwiftCommunity/RxDataSources” ~> 5.0
If you are using Xcode 11 or higher, go to File / Swift Packages / Add Package Dependency… and enter package repository URL https://github.com/RxSwiftCommunity/RxDataSources.git, then follow the instructions.