[Question] Is it really beneficial to have implicit filtering logic on value set?

[raveclassic]

[Question] Is it really beneficial to have implicit filtering logic on value set?

[raveclassic]

Hey @Nedgeva, thanks for the issue.
The main idea, as mentioned by @Fyzu, is that Property/Atom describe values, not sequences of events. There's no "timeline" concept for a Property/Atom, only its value and change notification. If value doesn't change (references are equal), there's no change notification.
Speaking about events, it's semantically incorrect to describe an "event" with a Property/Atom. We can only describe something like declare const lastClick: Property<MouseEvent | undefined> or declare const allClicks: Property<readonly MouseEvent[]>, due to the push-pull nature of frp-ts. If we want to describe infinite sequence of clicks, we should rather use a push-observable implementation like rxjs/most.

@Fyzu Good point. Documentation definitely needs improvements. I'll log a linked ticked and close this [Question].

[Fyzu]

I discussed about this with @raveclassic.
frp-ts not about events, about working with state.
If you need stream and every event is important, use something else. :)

[Fyzu]

@raveclassic I think we should warn about this behavior in the documentation. What do you think?