Feature Request: ability to rescue onContentError in collaborative environments

[zackdotcomputer]

Description

Currently the onContentError pathway as implemented by #5178 has a one-way function to destroy collaboration integrations for the editor in disableCollaboration(). This is useful for situations where the user has performed a fundamentally invalid behavior. But in situations where the cause of an error is understood and could be recovered from, this does not leave a pathway to resolve the error without either:

1. Syncing the error state followed quickly by the fixed state to other clients (requiring them also to handle the error)
2. Or else destroying the collaboration layer, meaning the recovered newest state cannot be synced.

Instead, I would like to be able to somehow hold the collaboration layer until the data schema is in a rescued state, and then continue with syncing. I don't know enough about the internals of TipTap yet to suggest how this would be best implemented - my naive first thought would be a Promise return type for onContentError that could return a new content for the editor?

Use Case

Specifically this is useful in our case where a nondeterministic system like an Agent creates edits to the document which are invalid but which can be rescued. We would like to avoid syncing these invalid edits to other users viewing the document, but we would also like to keep all users online.

Type

New feature

[zackdotcomputer]

Another option would be a enableCollaboration prop handed to onContentError so that the system could re-enable the collaboration extension after performing a rescue?