Batch actions

[arcanis]

Since each dispatched actions trigger an immediate render, a common pattern is batched actions. However, using them makes it quite harder to inspect what each action does (since you can only cancel batched actions, and not the individual actions that they compose).

It would be great if the extension was able to see that an action is a batched action (for example by checking its type against a specified property name), extract the actions inside (again by reading a configured property), and recreate this batched action without the canceled sub-actions.

[zalmoxisus]

Thanks for the suggestion. It sounds interesting, but better to implement on the monitor's side, whether on inspector or log monitor.

[kvanbere]

Any update? I would like to see this too. We batch real time websocket messages together to avoid severely excessive redraws, which makes the dev tools handy but confusing for us to look at (imagine, 10 lines of just 'BATCHED_ACTIONS' and not much substance).

We don't need to see the individual state changes, but if we could just see what actions were in each batch on the left pane underneath it or something it would be amazing.