You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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?
The text was updated successfully, but these errors were encountered:
inakianduaga
changed the title
Feature: Dev tools
[Feature] Dev Tools for visualising reactive flow
Nov 7, 2018
by appending ⬇️to each Observable returned by each epic
epic(...).pipe(tap(updateGraph(epic.name)))
by adding property epicName to action$ object we could...
append ⬇️to each action$
action$.pipe(tap(updateGraph(action$.epicName)))
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.
Should they be ignored? (in such case we'd only add first usage of action$ in a epic to the graph)
Should they be displayed differently as side-effecty actions?
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?
The text was updated successfully, but these errors were encountered: