That’s a neat idea (and I’ll probably use it at some point) but it doesn’t address the issue, which is that in Absinthe the subscription updates are handled asynchronously, so you can’t guarantee ordering/consistency between them and the initial state.
It would also require the un-merged “catchup” feature I linked earlier, but that, at least, is more or less a solved problem.
