RACCommand executionSignals error handling

[kastiglione]

I ran into a case that is likely rare, but thought I should document it. I don't expect any action to be taken on this.

Like in previous issues, I had a command whose signal block returns a signal that only completes or errors.

To handle the two cases, I had:

[command.executionSignals subscribeNext:^(RACSignal *execution) {
    [execution subscribeCompleted:^{
        // Triggered by error
    }];
}];

[command.errors subscribeNext:^(NSError *error) {
    // Triggered by error
}];

The cause is this catchTo:[RACSignal empty], but since it can't be made [RACSignal never], it is what it is.

[jspahrsummers]

You can use -materialize on your created signal to circumvent the filtering.

[kastiglione]

ℹ️