Description
We’re seeing rendering issues in draft-js-import-markdown@1.4.1 where paragraphs and list blocks are not parsed correctly unless they are explicitly separated by a blank line (\n\n). This results in structured content collapsing into a single paragraph or failing to render list formatting even when the Markdown appears syntactically correct.
Example
Input Markdown:
After the call\n1) List item one\n2) List item two
Actual rendering:
After the call1) List item one2) List item two
Workaround
As a short-term workaround, we’re pre-processing the Markdown to:
- Insert \n\n between list blocks and the next paragraph
- Insert \n\n before list blocks if they follow plain text or headings
Description
We’re seeing rendering issues in draft-js-import-markdown@1.4.1 where paragraphs and list blocks are not parsed correctly unless they are explicitly separated by a blank line (\n\n). This results in structured content collapsing into a single paragraph or failing to render list formatting even when the Markdown appears syntactically correct.
Example
Input Markdown:
After the call\n1) List item one\n2) List item twoActual rendering:
After the call1) List item one2) List item two
Workaround
As a short-term workaround, we’re pre-processing the Markdown to: