Option to emit the initial observable value about signalkit HOT 5 CLOSED

Hi,

Actually it was the desired effect to dispatch the current value when adding an observer to ObservableValue. Thanks for pointing out the bug!

Just released the v0.1.1 with the bug fix.

Thanks!

from signalkit.

Thanks for the quick fix. Do you accept PR to add other methods, e.g. flatMap?

On Jul 27, 2015, at 3:32 AM, Yanko Dimitrov [email protected] wrote:

Hi,

Actually it was the desired effect to dispatch the current value when adding an observer to ObservableValue. Thanks for pointing out the bug!

Just released the v0.1.1 with the bug fix.

Thanks!

—
Reply to this email directly or view it on GitHub.

from signalkit.

Sure, flatMap will be a great addition.

from signalkit.

Pardon for digging this back up, but even though I dig the most recent rewrite, it looks like this feature of emitting the initial observable value has not survived. This doesn't much affect my code that does observe().next() { myupdatemethod() } since I can call my method separately during load, however it does impact where I'm currently using 'observe().bindTo(...) for which there's not an obvious thing to call manually.

This is only from looking at the (now much simpler!) code, I might be wrong. Can you verify this has indeed changed since v3.0?

If this is the case, what's a good approach get this behaviour back: maybe add my own extension SignalType which adds bindToAndEmitInitialValue, or use a new SignalEmittingInitialValue (conforming to SignalType) instead of Signal?

from signalkit.

Its functionality moved to SignalValue which is a signal that holds its most recent value and when you observe it you will receive right away the current value.

I need to find some time to update the library to Swift 3 and perhaps rework some parts.
If you have any suggestions, please open an issue.

:)

from signalkit.