Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Transactions should probably be observables #80

Closed
nhunzaker opened this issue Oct 19, 2015 · 0 comments
Closed

Transactions should probably be observables #80

nhunzaker opened this issue Oct 19, 2015 · 0 comments

Comments

@nhunzaker
Copy link
Contributor

For background, whenever an action is pushed into Microcosm via app.push, it runs coroutine on the value returned from the action. There are 3 states returned from coroutine: progress, fail, and done. This is very similar to how Observables work, and I would love to expose interoperability with transactions to libraries like Rx. At the very least, use an already existing pattern that is well established in the community.

If we did this, is it feasible to make it compliant with RxJS? https://github.com/Reactive-Extensions/RxJS. We have our own scheduler, dispose strategy, and observation pattern - would it be too hard do this? How could we mitigate as many breaking changes as possible?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant