[Bug]/[Feature] Parser error with non-standard markdown content. Ability to suppress errors?

[PickleyD]

Initial checklist

• I agree to follow the code of conduct
• I searched issues and discussions and couldn’t find anything (or linked relevant results below)

Affected packages and versions

7.4.0

Link to runnable example

No response

Steps to reproduce

Go to playground and enter - <!-- A comment --> in the raw markdown side.

Expected behavior

An error occurs but the editor remains responsive. - <!-- A comment --> appears as plain text in the markdown viewer/editor.

Actual behavior

Observe error in console of Uncaught (in promise) MilkdownError: Create prosemirror node from remark failed in parser... and editor crashing.

Is it possible for a consumer of the editor to configure it to catch/suppress errors such as this coming from the parser (and just parse the content as plain text), to avoid any full editor crashes resulting from unusual user input?

Runtime

Chrome

OS

macOS

Build and bundle tools

No response

[kessiler]

@Saul-Mirone any suggestion on how to deal with this? I'm having similar problem, but parsing a table.
Example:

|    |
| :- |

In Github, it parses fine. This seems to be an issue in transformer, at least for tables. (It doesn't set an empty property children for tableRow)