Is it valid to start actions in onActionMiddleware's onStart/onFinish?

[PEZO19]

Is it valid to start actions in onActionMiddleware's onStart/onFinish?

[xaviergonz]

another alternative would be to mark the mapped object as "dirty" and make the mapped object recalculate on "get" if dirty is true

[PEZO19]

@xaviergonz Regarding #519 (comment):

My point is about having the freedom to eliminate "recalculation" (from scratch). I am totally fine if 95% of my app works with recalculation (it's easier to reason about + simpler code), but that 5% must rely on deep observation and listening to deep changes and propagating these deep changes solely. Also, this part must be reactive and can not be passive. (Explicit mutation of mapped is not good enough, does not scale regarding DX.)

As onPatches does not help inside of a transaction, my attempts was to treat actions like these changes events which "needs to be propagated". For that, I'd need the freedom to nest "onAction"s and as part of that, to emit new actions.

Just and idea: it would be nice if we could insert a callback (eg used with standaloneAction) before and especially after an action. So, beyond onStart and onFinish there could be a beforeStartStandaloneAction and afterFinishStandaloneAction - as sibling actions, respecting the boundaries.

However it would be also interesting something like afterStartStandaloneAction and beforeFinishStandaloneAction which could be ("pseudo")children actions of the target action, called before/after anything else in the action.

Is my assumption good, that currently it is not valid to start actions in onActionMiddleware hooks?