Should `executing` be emitting `false` as first value ?

[c0diq]

ReactiveCocoa contract was that the executing observable would emit false as a first value when subscribed to and the command was not executing. This would allow to directly use it in the enabledIf of another opposite action. Instead we have to manually send false which can have side effects if the action is actually executing.

let stopAction = Action<(), ()> { _ in .just(()) }
let startAction = Action<(), ()>(enabledIf: stopAction.startWith(false).not()) { _ in
   .just(())
}

Instead of

let stopAction = Action<(), ()> { _ in .just(()) }
let startAction = Action<(), ()>(enabledIf: stopAction.not()) { _ in
   .just(())
}

[ashfurrow]

That makes sense to me – are you able to open a PR adding this behaviour (and a test)?

[dangthaison91]

@c0diq Just do a quick check and executing always emit false first? You can refer to this line of code:

Action/Sources/Action/Action.swift

Line 106 in 6ee7429

.startWith(false)