Modularize mux and demux

[tusharmath]

mux and demux are some awesome util functions. It would make a lot of sense to take it out of this project as a standalone dependency.

[milankinen]

Hmmm. That's very interesting proposal. I don't see it impossible to extract core transforms into separate module, e.g @tsers/prelude. It might even clear the codebase.

[tusharmath]

@milankinen Does it have to be a part of tsers? I mean, it could be a completely different module which is stream agnostic too.

[milankinen]

mux and demux use only map and filter so that is indeed possible! Do you want to create a new npm module and copy those functions into it (it's fine for me)? Or do you want that I'll do that?

[tusharmath]

@milankinen I would be glad to create a separate module. What would you want to call it?

[milankinen]

That is a hard question. Something related to signal processing perhaps? I'm counting on your judgement in this matter. 😄

[tusharmath]

Here it is — https://github.com/tusharmath/muxer Will create a pull request with this as a dep.

[milankinen]

Nice 👍

[tusharmath]

@milankinen What is the purpose of demuxCombined in this module? I have not seen it being used in anywhere and quite a lot of test cases have been written for it.

[ghost]

@tusharmath check https://github.com/tsers-js/examples

[milankinen]

demuxCombined must be used if you have an observable containing an array of muxed observables (usually when you're dealing a list).

Like @pmros pointed out, an example usage can be found here: https://github.com/tsers-js/examples/blob/86810a6cbe76e63cf35493a7005fe9547ec62b48/examples/counter-list/index.js#L32-L43

[tusharmath]

@milankinen This should too be out of the package isn't it?

[milankinen]

It's up to you to decide that. 😄 I'm fine with both options (in/out).

There is not much code, though: https://github.com/tsers-js/core/blob/master/src/index.js#L72-L78