From 929f4f11d899e9530689e1ae04c9bf24bc94f8f3 Mon Sep 17 00:00:00 2001 From: Pol Quintana Date: Fri, 11 Dec 2015 11:59:29 +0100 Subject: [PATCH 1/2] Update RRC version to 0.3.0 --- README.md | 9 +++++---- RealmResultsController.podspec | 4 ++-- 2 files changed, 7 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 11c8fcf..331b4db 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,5 @@ -![](https://img.shields.io/badge/coverage-100%25-green.svg) ![](https://img.shields.io/badge/language-swift-blue.svg) -![](https://img.shields.io/badge/version-0.2.5-red.svg) +![](https://img.shields.io/badge/version-0.3.0-red.svg) ![](Images/RRCHigh.png) @@ -37,6 +36,8 @@ The `RealmResultsController` needs 4 parameters: Where `T` is a `Realm` model and `U` is the type of the object you want to receive from the RRC. Since the RRC works in background, we can't work with normal Realm objects, so we either create mirror copies of the objects not associated to any Realm, or we map the Objects to another kind of "entity" of type `U` +The operations the RRC has to execute are enqueued to avoid unordered calls to `willChangeResults` and `didChangeResults` + __Note:__ `T` and `U` can be of the same type, then the RRC will return a copy of the `T` objects but not included in any Realm. __:heavy_exclamation_mark: what is the `filter` for?__ @@ -257,7 +258,7 @@ To use the demo, just run the following command to install the Realm dependencie #### Carthage: ``` -github "redbooth/RealmResultsController" "0.2.5" +github "redbooth/RealmResultsController" "0.3.0" ``` #### CocoaPods: @@ -265,7 +266,7 @@ github "redbooth/RealmResultsController" "0.2.5" ``` use_frameworks! -pod 'RealmResultsController', '~> 0.2.5' +pod 'RealmResultsController', '~> 0.3.0' ``` #### Manual: diff --git a/RealmResultsController.podspec b/RealmResultsController.podspec index 4013e55..a513b94 100644 --- a/RealmResultsController.podspec +++ b/RealmResultsController.podspec @@ -1,11 +1,11 @@ Pod::Spec.new do |s| s.name = "RealmResultsController" - s.version = "0.2.5" + s.version = "0.3.0" s.summary = "A NSFetchedResultsController implementation for Realm written in Swift" s.homepage = "https://github.com/redbooth/RealmResultsController" s.license = 'MIT' s.author = "Redbooth" - s.source = { :git => "https://github.com/redbooth/RealmResultsController.git", :tag => "0.2.5" } + s.source = { :git => "https://github.com/redbooth/RealmResultsController.git", :tag => "0.3.0" } s.platform = :ios, '8.0' s.source_files = 'Source' s.frameworks = 'UIKit' From 39b795a770377bfee06fe83bfee868c20ab234a6 Mon Sep 17 00:00:00 2001 From: Pol Quintana Date: Fri, 11 Dec 2015 12:04:16 +0100 Subject: [PATCH 2/2] Updated description --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 331b4db..d9623f3 100644 --- a/README.md +++ b/README.md @@ -36,7 +36,7 @@ The `RealmResultsController` needs 4 parameters: Where `T` is a `Realm` model and `U` is the type of the object you want to receive from the RRC. Since the RRC works in background, we can't work with normal Realm objects, so we either create mirror copies of the objects not associated to any Realm, or we map the Objects to another kind of "entity" of type `U` -The operations the RRC has to execute are enqueued to avoid unordered calls to `willChangeResults` and `didChangeResults` +Operations on each RRC are enqueued to avoid unordered calls to `willChangeResults` and `didChangeResults`. Each RRC has its own queue. __Note:__ `T` and `U` can be of the same type, then the RRC will return a copy of the `T` objects but not included in any Realm.