Transforms

[asarazan]

Do we want a transform "pipeline" such that we can essentially map the values coming out of a bismarck? Theoretically you could rig this up pretty easily on top of the existing eachValue flow. See RescopedBismarck for inspiration.

[treelzebub]

I'm not against this, but it could be a slippery slope. It might be useful for us to have a chat where we outline the boundaries and guiding principles for Bismarck. Key questions:

• What should live in the core lib and what should be provided as extensions?
• What is the value of providing bismarck transforms if extension libs for Flow, RxSwift, and RxJava exist?
  • If the answer is "making it trivial to provide such extensions" then I'm open to seeing an example.

[treelzebub]

*actually Flow should just be provided out of the box and i think that's the answer to this Issue.

[asarazan]

Hard agree on having a live discussion on all this.

In this case the transform acts on the data itself, not the wrapper/channel/flow. e.g. sanitizing, or just converting an API type into a more easily-used client type.

[treelzebub]

cool, let's set up a call soon. that should take care of a lot of my wrongthink ;)