Currently, these will propagate up the stack and the leave the app in an inconsistent and possibly stuck state. This behavior is okay for local operations (crash the app without affecting any collaborators), but probably not when receiving remote messages - a single bad message could make a doc unusable.
It would be nice to find a better way to handle these errors. In particular, we could ensure that all parts of a transaction that don't cause an error go through normally, including the vector clock update and messages for other CRDTs.
Due to custom Collab implementations and https://github.com/composablesys/collabs/issues/257, we should occasional errors in
Collab.receivemethods.Currently, these will propagate up the stack and the leave the app in an inconsistent and possibly stuck state. This behavior is okay for local operations (crash the app without affecting any collaborators), but probably not when receiving remote messages - a single bad message could make a doc unusable.
It would be nice to find a better way to handle these errors. In particular, we could ensure that all parts of a transaction that don't cause an error go through normally, including the vector clock update and messages for other CRDTs.