Adds extensions for Codable in the same manner the we already have extensions for Marshal

And as Realm 5.3 requires iOS 9.0+, I've also bumped deployment targets of our Realm extensions.

• uses ReactiveSwift from version 7.0
• uses ReactiveCocoa from version 12.0
• uses AlamofireImage from version 4.0
• changes iOS deployment target to 10.0

Bumps addressable from 2.7.0 to 2.8.0.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Using completely custom queue was not really correct as RealmCollection changes were propagated on incorrect thread. This solution tries to use current queue, instead of nil queue, so it should probably fix issue from #56 and also preserve correct thread.

Please @LukasHromadnik run it on your Mac and if it is fine, then we can merge it.

Lately, we have experienced several crashes after updating Realm dependency in project which also uses ACKReactiveExtensions. Given PR should resolve the issue.

• build using Xcode 12.4
• update workflow to use XCFrameworks - uses custom action that uses Carthage workaround script as Realm currently doesn't contain M1 archs when building (https://github.com/realm/realm-cocoa/pull/7095)
• update dependencies

Right now we depend on ancient Realm version ~> 3.14 as current version is 4.3.2 and 5.0.0 is in its third beta, it might be time to update our dependency to at least ~> 4.0 so everyone who uses this version can still use our lib and later on to release version with ~> 5.0 support.

Ocassionally if Realm receives new data before sending initial change notification, it just sends initial notification with modified content (e.g. if data is saved on other thread). So the skip(first: 1) would actually skip a change.

Checklist

• [ ] Updated CHANGELOG.md.

This PR addresses #40. It adds deprecations to extensions which are available through keypaths so they can be removed in later releases.

Right now I am not sure about the deprecation style - maybe this way would be better?

@available(*, deprecated, message: "Use [\.tableHeaderView] instead")

Checklist

• [x] Updated CHANGELOG.md.

As we do not like the force cast of error, we should use generic MappingError also for Marshal extensions (in the same way we do it for Codable)

https://github.com/AckeeCZ/ACKReactiveExtensions/blob/d7ced4c5e685a56099187d31542a302f9109a0fa/ACKReactiveExtensions/Marshal/MarshalMapping.swift#L61

Do we want to update the AlamofireImage dependency to ~> 4.0? The point is that it already depends on Alamofire ~> 5.0 but we haven't updated it in our projects which might be a bit annoying as it means some effort.

Updating it in ACKReactiveExtensions would mean that we will not be able to update it until we update Alamofire in project.

ReactiveSwift allows accessing allows accessing reactive properties using KVC

tableView.reactive[\.tableViewHeader] <~ tableViewHeaderSignal

We can compact ACKReactiveExtensions by removing such extensions

Use case

When adding images to UIImageView using AlamofireImage, the binding target extension should be of type BindingTarget<URL?> for simple reason. If new imageURL is set AlamofireImage automatically cancels running request for previous URL (if any). But if new model has no imageURL, then imageView.af_cancelImageRequest() should be called to cancel current image request (if any).

Possible solution

There are two possible solutions:

1. Add imageView.reactive.cancelImageRequest: BindingTarget<Void> and call it if nil is assigned
2. make imageView.reactive.imageURL of type BindingTarget<URL?> and if nil then imageView.af_cancelImageRequest() will be called

I'd prefer the 2nd solution as it fits our needs best.

https://github.com/AckeeCZ/ACKReactiveExtensions/blob/145af295341226f41202450314129a08c8d80f2a/ACKReactiveExtensions/AlamofireImage/AlamofireImageExtensions.swift#L14