Feature Request: option to disable parseHTML when contentType is markdown #7393
nicoknoll
started this conversation in
Feature Requests
Replies: 1 comment
-
|
I really need this option, without it I have to write a lot of crooked hacks |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Description
Hello, right now I'm using the editor with contentType set to "markdown".
I insert content via:
and get it out of the editor with:
So basically I try to use it in "markdown-only mode". The issue I came across now is that when a user writes "bla" into the editor it is displayed correctly. When I check the state outside its a string containing this.
Now I allow users to edit their content. Therefore the string is inserted via the method shown above. Because the string contains valid html it gets parsed by the extensions as html and the editor only shows "bla".
With a span tag this is no issue I guess but thinking further this way users could include arbitrary html content as long as it can get parsed by the extensions. Additionally the content gets changed which is weird for the user as well.
So I would like to propose an option on the Markdown extension like:
which should disable the extensions html parsing. Maybe when using contentType markdown something like this should be enabled by default?
P.S.: It seems like this was possible before using html: false, I guess thats why claude and chatgpt kept proposing that. But I guess marked / custom MarkdownManager doesn't support that anymore ?
Use Case
Use case is when entering html tag like content into a contentType markdown editor.
Type
New Tiptap API
Beta Was this translation helpful? Give feedback.
All reactions