I’m wondering what the danger of mismatched transactions is when the editor state appears correct, history correct, decorations correct - everything seems to be correct.
We get this when we chain a selection-related command after the
splitListItem command but I can’t find any harms that seem to come from this error no matter how vigorously I test it and try to break the editor after this mismatched transaction occurs.
Are all mismatched transactions inherently dangerous? Is there any harm to wrapping this command in a
try/catch block and moving on with our work? The alternative would be to make a gnarly custom command, but that seems hard to justify since the current code seems to work.