Strider
Strider
@irisjay, this bothered me as well. As far as I remember, I ended up using [`_.flow`](http://lodash.com/docs#flow) to compose all of functions and then apply them at once. But I miss...
@irisjay, > how do you think this issue relates to the aesthetics of flyd? As I said before, I miss fluent sometimes. And I use fluent extensively on native `Array`....
@paldepind, ye, that's it. ☝️
> This special casing would also have to be built in to most flyd modules (unless I'm mistaken). This increases complexity. I'm worried about this part most of all. I...
@RangerMauve, other modules can rely on this.
@spion > they like to pretend promises don't exist Damn right. The only stream lib which has seamless promise integration I know is [Flyd](https://github.com/paldepind/flyd).
@pocesar, hm, your snippet does not represent my idea, since it relies on base `coalesce`. Consider `obj.path = null` (but present) and `obj.path2 = true`. Base `coalesce` will return `null`...
@pocesar, thanks, no testing required, I've looked through your updated version and it's a solution. I think such thing must be in core, since it's a very low-level code and...
@pocesar, of course it can save compability. This can be done with boolean parameter or predicate for `coalese` or even distinct function.
@pocesar, I have an idea of such design: `.first(object, paths[], predicate = Boolean);` > — for every `path` in `paths` checks if `path` is present and the `predicate(value, path, object)`...