An global interceptor?

@danieleneal^^^

See FAQ on how to set one up

https://github.com/Day8/re-frame/blob/master/docs/FAQs/GlobalInterceptors.md

cool, yep used a global interceptor thanks!!

@danieleneal the other way you can do it, which is not quite as good IMO, but I'll include it for completeness is ...

to create your own version of dispatch. Let's call it emit

And then you make email log whereever it needs to about what event is being queued, before then actually calling dispatch

The problem with this method can be (in some cases) that lots of events are dispatched in a hurry, and although you are log them all ... later on you are not sure which one you are currently processing. Generally speaking this method can work reasonably. You emit an event and then handle it. Then you emit another one, then handle it, etc. There's only ever one event at a time. BTW, the other problems with the emit approach is that you then have to use an effect handler :emit rather than :dispatch. Which means yo uhave to write that effect handler too.

So, yeah, not as good. But mentioned for completeness

Since we use re-frame we live in the future already, but here's a nice article I found about changing states. (also dips into api states, etc.) https://josephg.com/blog/api-for-changes/