redux-observable / redux-observable

RxJS middleware for action side effects in Redux using "Epics"
https://redux-observable.js.org
MIT License
7.85k stars 468 forks source link

[Feature] Dev Tools for visualising reactive flow #587

Open inakianduaga opened 5 years ago

inakianduaga commented 5 years ago

Do you want to request a feature or report a bug?

Feature

What is the current behavior?

There is no easy way to gain observability on the RX data flows except for manually adding debugging info inside the code. This might not be so easy since redux-observable ultimately lets you do whatever RxJS does, but a monitoring tool like

https://github.com/redux-saga/redux-saga-devtools

would be very useful in terms of easily understanding reactivity inside an app (some things related to redux actions are visible via regular redux-devtools but "non-action" processes are "invisible".

Are there any plans in this direction?

zepod commented 5 years ago

Idea on how this could be done....

Directed graph 1) where actions are nodes and epics are edges 2) where actions are edges and epics are nodes

Not sure if 1) or 2) is better

The graphcould be printed onto the screen (either chrome ext. or iframe in the app?).

Collection of nodes and edges would be continuously updated during runtime, as more epics would get activated.

updateGraph fn is kinda hard to think about 🙄but surely could be figured out

Another question that is hanging in the air is how should be references to non-input and non-output actions displayed on the graph. I mean those references used for takeUntil etc.

So the questions are

tylerweitzman commented 5 years ago

+1 any update on this?