@urbanslug hmm, I don't really understand the question.

Hi. I have 2 events which are each causing 1 separate change in the re-frame db. I would like to find a way to avoid the view from rendering between those 2 db changes so that each time the view is re-rendered it never sees inconsistencies. What would be the best way to do that?

@vincent.cantin if you know there will always be two events could you queue the changes from the 1st event and process them in the 2nd event with the changes from the 2nd event?

That’s what I am currently doing, but I wanted to know if there were other solutions.

Does dispatch-sync cause subscription reaction immediately or it will happen asynchronously on the next rendering cycle?

Do people usually register event handlers for each field in an entry/submission form?