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

explore removing rxjs as a dependency in @tdm/data #5

Open
shlomiassaf opened this issue May 12, 2017 · 0 comments
Open

explore removing rxjs as a dependency in @tdm/data #5

shlomiassaf opened this issue May 12, 2017 · 0 comments

Comments

@shlomiassaf
Copy link
Owner

shlomiassaf commented May 12, 2017

Currently, @tdm/data depends on the RXJS observables library and uses it to manage logic and workflow.

Since it is a core library, it's better not to enforce a 3rd party library that might be used on an application only by @tdm/data.

RXJS is used in 3 places:

Events

The events are completely RX based, there is one event stream (hot) from which all events come from.

Effort: Hard

Plugins (resource-control)

Extends the root event stream and filter events based on their instance origin.
From there, each instance's event stream is split into logical events that expose stream such as busy, self etc.

Effort: Hard

Action controller (action flow)

The actions controller handles an action flow, the whole flow is RX based.
In addition, each adapter must implement an execute function that returns an observable.

Effort: Easy / Meduim

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

No branches or pull requests

1 participant