Skip to content
This repository has been archived by the owner on Feb 16, 2020. It is now read-only.

Commit

Permalink
Merge branch 'master' into 07.queries
Browse files Browse the repository at this point in the history
  • Loading branch information
Juan Mendez committed Mar 29, 2017
2 parents db81ba8 + 81d10a7 commit cfe895e
Showing 1 changed file with 6 additions and 2 deletions.
8 changes: 6 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,13 +16,17 @@ What has been done so far
- Asynchronous and synchronous transactions with RxJava
- Schedulers for testing use Schedulers.immediate()
- Support or() for chaining queries
- realmQuery.distinct(*), realmResults.distinct() has been deprecated in Realm 3.0.0
- realmQuery.sort(*), realmResults.sort(*)
- Grouping
- Querying against realmResults
- delete reamModels in cascading mode
- support also for deleting methods found in realmResults, realmModel, realmObject and realmLists
- support realmQuery.*Async() methods
- realmResults.addChangeListener(), realmObject.addChangeListener()
- realmResults.asObservable(),realmObject.asObservable()
- realmResults.asObservable(),realmObject.asObservable(), not supporting realm.asObservable() at this time
- Several features not covered will simply pass, and not perform anything. In this situation, I am going to include a console message with prefix `#Mocking-Realm` and let you know when that occurs. The same rule will apply for features which I cover partially. For example during mocking Realm I couldn't track their annotations, due to their retention type. So I am just going to let you know to make sure include `@Index` in your attributes when required to use realmQuery.distinct(*) for instance.

What is coming next
- A chart with what's being covered and what is not from RealmModel, RealmObject, RealmQuery, RealmResults, and RealmList
- Cover RealmQuery.not()
- Finally a chart with what is covered, and what will be mocked to be ignored.

0 comments on commit cfe895e

Please sign in to comment.