Closed PhilippeCuvillier closed 2 years ago
Thanks a lot for contributing @PhilippeCuvillier! I've invited you to join the RxSwiftCommunity GitHub organization – no pressure to accept! If you'd like more information on what this means, check out our contributor guidelines and feel free to reach out with any questions.
Generated by :no_entry_sign: dangerJS
Any update on releasing this PR? Current production code is evading anyone rather than RxRealm
to correctly define reactive extensions on Realm. Merging this PR would thus make this library compliant to how rx
should be defined or extended.
@freak4pc this is the PR for #174 . It will make this pod/package standard with regards to other Rx extensions.
hmmm for some reason the Release Action has not been triggered.. any idea how the merged PR can appear in the Cocoapod repository or is it just a matter of time?! @freak4pc
PS: Thanks for merging... 🙏
Starting from RxSwift 6.1 version, it is – again – possible to use the somehow standard
rx
attribute ofReactiveCompatible
protocol extension on a non-class type likeRealm
. (https://github.com/ReactiveX/RxSwift/pull/2285)This would again allow users of RxRealm to define their custom
realm.rx.someCustomMethod()
extension methods along with RxRealm ones. Ex:Defining such extension is currently not possible as the ad hoc
rx
extension of RxRealm has abase
attribute withprivate
visibility, which prevents from using it in custom methods outside this pod.