You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I posted on StackOverflow here, and I think this may be a bug.
I've been searching for a while now, and I can't seem to find any one mentioning this issue.
We use TipTap / ProseMirror as a text editor, and prosemirror-markdown's default serializer/parser utilize backslash-preceded newlines (\\n) to denote soft breaks. It does seem that double space preceded newlines work as expected ( \n)
The issue is that the backslashes are rendered in the parsed jsx, even though I think (\\n) is valid and preferred since its visually clearer when viewing the plain text version of the markdown.
The text was updated successfully, but these errors were encountered:
neaumusic
changed the title
Explicit hard breaks don't seem to be converted as <br>
Explicit soft breaks don't seem to be converted as <br>
Sep 27, 2024
I posted on StackOverflow here, and I think this may be a bug.
I've been searching for a while now, and I can't seem to find any one mentioning this issue.
We use TipTap / ProseMirror as a text editor, and prosemirror-markdown's default serializer/parser utilize backslash-preceded newlines (
\\n
) to denote soft breaks. It does seem that double space preceded newlines work as expected (\n
)The issue is that the backslashes are rendered in the parsed jsx, even though I think (
\\n
) is valid and preferred since its visually clearer when viewing the plain text version of the markdown.The text was updated successfully, but these errors were encountered: