Fork me on GitHub

I was looking through re-frame CHANGELOG and found this

1.1.0 (2020-08-24)
re-frame now guarantees that a :db effect, if present, will be actioned before any other sibling effects. re-frame continues to provide no guarantees about the order in which other effects will be actioned.
I was pretty sure that re-frame already guaranteed that :db is actioned first before 1.1.0. Am I wrong?


You are. You're probably thinking of this effect map:

{:db (...)
 :dispatch [...]}


Here, the effects are unordered. But the event is handled after the :db effect is handled simply because :dispatch doesn't handle the event itself - it just schedules it.

👍 6