Could the markdown conversion convert unsupported attributes to plain text insead of throwing an error?

[maelchiotti]

Is your feature request related to a problem? Please describe.

When using text formatting in the editor that isn't supported in markdown (such as underlining), it breaks the conversion to markdown since the attribute cannot be handled.

Describe the solution you'd like

If you want to keep this behavior, maybe an option could be added to just treat those attributes as plain text? It would allow me to export text even if it has some unsupported markdown in it. This option would be opt-in, and I would handle warning my users.

Describe alternatives you've considered

I don't really know, I could just skip all the notes in my app that cannot be fully converted to markdown, but skipping a huge note just for one underlined word is a shame 😕