reactivecocoa / reactiveobjcbridge Goto Github PK

Was trying to update ReactiveSwift 1.1.1 but ReactiveObjCBridge seems to depend on ReactiveSwift 1.0 ?

The README.md reads:

“Hot” RACSignals cannot be directly converted into Signals, because any RACSignal subscription could potentially involve side effects. To obtain a Signal, use RACSignal.toSignalProducer followed by SignalProducer.start, which will make those potential side effects explicit.

I have an instance of RACSignal due to a mixed-language project. Looking through XCode's auto-completion suggestions, I'm not seeing anything like toSignalProducer.

Could I get a code example of how to turn a RACSignal back to Signal?

Thanks!

@andersio @ikesyo Would one of you mind pushing 3.1.0 to trunk, or alternatively adding me as an owner?

extension Action { fileprivate var isEnabled: RACSignal<NSNumber> { return self.isEnabled.producer.map { $0 as NSNumber }.bridged } }

Gives error: Value of type 'RACSignal<NSNumber>' has no member 'producer'

With cocoapods 1.5.2 I am getting the error:

The Swift pod `ReactiveObjCBridge` depends upon `ReactiveObjC`, which do not define modules. To opt into those targets generating module maps (which is necessary to import them from Swift when building as static libraries), you may set `use_modular_headers!` globally in your Podfile, or specify `:modular_headers => true` for particular dependencies.```

This is right now just a producing a lot of compilation warnings, however, would be good to be prepared for ReactiveSwift 2.0

There is an issue like this

The Swift Language Version is 4.0 .
I have no idea about this.

Hello. The released version contains outdated podspec files, as far as CocoaPods do not know anything about version 5.0.0: the master repo still refers to 4.0.0 version. It would be great to have both up-to-date

carthage update fails on Xcode10.2.

ReactiveSwift/Sources/Scheduler.swift:187:18: error: 'Hashable.hashValue' is deprecated as a protocol requirement; conform type 'DispatchSourceTimerWrapper' to 'Hashable' by implementing 'hash(into:)' instead
        fileprivate var hashValue: Int {
                        ^

** ARCHIVE FAILED **

Probably need ReactiveSwift 5.0 dependency.

Hi there! A recent regression makes this repo fails to type check on Swift master: https://bugs.swift.org/browse/SR-7341. It's still not fixed, and it's unclear whether or not this will be fixed. I suppose this is more of a PSA, but there are some possible next steps:

1. Change the name of one of the isEnabled properties in question (not ideal).
2. If you feel so inclined, contribute a patch to Swift that fixes the regression or help find someone who can do so.
3. Figure out how to add this repo to https://github.com/apple/swift-source-compat-suite

This last step would help both prevent issues and the future and raise more awareness about the current issue. Given the dependencies in this repo, I think a separate repo would need to be opened by the maintainers (part of the "Have maintainers who will commit to resolve issues in a timely manner" requirement of that suite) that includes all of the dependencies in a single project.

Thanks for your time and consideration!

I use the "ReactiveObjCBridge" master branch to pod install. But Recently, I just pod install without modify any version (still use master), found that the "value" parameter is changed to internal, so that I can not use it anymore. Could you please help to share what can I do then ?

Here is the old code sample:
guard let value = event.value else { return }

Any idea for this ? Thanks a lot.

I'm not sure how useful this would end up being nor how much can actually be done given the constraints involved (such as the impossibility to know at runtime how many elements a Swift tuple holds, etc.).

However, I thought I'd have a look to see what could be done. If I finish anything that looks reasonable, I'll create a pull request.

Being able to bridge a RACTwoTuple<NSString, NSNumber> into (NSString, NSNumber) would be quite useful. For instance when we have bridged our RACSignal<RACTwoTuple<NSString, NSNumber>> (do we actually retain nested types like this? I'm not sure) to a SignalProducer<RACTwoTuple<NSString, NSNumber>, NSError>, it'd make it easy to map that to get a SignalProducer<(NSString, NSNumber), NSError>.

Being able to turn a (String, Bool) into a RACTwoTuple<NSString, NSNumber> would also be useful when bridging to RACSignal.

I'm going through some of my Cartfiles and noticed that this repo still doesn't have a release tag set yet. Is there anything that we're waiting on before throwing a 1.0.0 on this?