Feature/notification based observation

[marshallxxx]

Add notification based NSManagedObjectContext change observation.

This adds two extra reactive extension to NSManagedObjectContext:

1. Observable for any context changes
2. Observable for object change in context

This would allow us later to create an observable with NSFetchRequest which will be notification based instead of NSFetchedResultsController. Benefits would be that every time a relationship of a type is changed we can trigger next value.

[freak4pc]

This is a really large change, and I don't use Core Data enough to review it.
I'm wondering if there's any way to split this into smaller PRs, or would you say this is a singular feature?

Thanks,
Shai.

[freak4pc]

Can you explain the version bump here?

[marshallxxx]

CocoaPods will not be able to resolve RxSwift dependency, as Podfile requires version ~> 4.0.0, while RxCoreData.podspec specifies ~> 4.2.0

[bobgodwinx]

@freak4pc I will give a look on Monday. However @marshallxxx it looks promising. 👍🏿

[marshallxxx]

@freak4pc agree, it looks quite large. But mainly it's addition of ManagedObjectContextNotificationObserver.

I've moved few things around, like NSManagedObjectContext+Persistable 😬, which adds extra changes.

[bobgodwinx]

@marshallxxx Can you re-base this to use the new RxSwift 4.3.1 Thanks

[bobgodwinx]

Hi @marshallxxx Sorry we totally forget the PR. I reviewed it and I think it's great. I like the idea of Notification based change sets. Are you willing to clean it up and rebase to the current master? If you don't have time I can pick it up myself. But it would great if you just rebase the changes. Thanks