Should KVO subscribables send their current value on subscribe? about reactivecocoa HOT 7 CLOSED

Why not just accept KVO options (which include the option to receive an initial notification)?

from reactivecocoa.

Maybe, but that'd require a bit more support for propagating the change dictionary. Which might be good to have anyways, but seems separate from this particular issue.

from reactivecocoa.

I mostly call it from a macro, so it's easy to switch between RACAble and RACAbleWithStart depending on whether I want the initial value or not.

I don't think much of my code would break if this behaviour was changed, and even the parts that did break would be trivial to fix, but I'd still rather have the option to choose whether I want the initial value or not, after all you do get the option with vanilla KVO.

from reactivecocoa.

@joshaber The change dictionary is mostly orthogonal — just make it clear you can't get new/old no matter what. Initial and prior options are still really useful.

from reactivecocoa.

Closing this for now. I think the real problem is that it can be hard to know if you need to use RACAbleWithStart instead of RACAble to get the behavior you want. This might just be papering over the issue.

from reactivecocoa.

@jspahrsummers :

just make it clear you can't get new/old no matter what.

Why is this? -rac_addObserver:forKeyPath:options:queue:block: doesn't look like it would have issues with it.

from reactivecocoa.

I mean that you wouldn't be able to get KVO "diffs", like added/removed objects in an array (obtained from the KVO change dictionary, as generated by NSKeyValueObservingOptionNew or NSKeyValueObservingOptionOld), because that would mean that the signal is sending different kinds of values at different times.

from reactivecocoa.