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
Hi,
I'm using this project to generate MDX files from our schema to feed into a Docusaurus static web site for documentation. It seems the md_nested template generates non-compliant Markdown with MDX due to mixing inline and newline styles.
Here's a snippet that's generated and where the mdx compiler gets upset:
Error: MDX compilation failed for file "/home/tom/repos/git-proxy/website/docs/configuration/reference.mdx"
Cause: Expected a closing tag for `</strong>` (19:1-19:10) before the end of `paragraph`
Details:
{
"column": 1,
"message": "Expected a closing tag for `</strong>` (19:1-19:10) before the end of `paragraph`",
"line": 19,
"name": "19:1-19:125",
"place": {
"start": {
"line": 19,
"column": 1,
"offset": 678,
"_index": 0,
"_bufferIndex": 0
},
"end": {
"line": 19,
"column": 125,
"offset": 802,
"_index": 1,
"_bufferIndex": -1
}
},
"reason": "Expected a closing tag for `</strong>` (19:1-19:10) before the end of `paragraph`",
"ruleId": "end-tag-mismatch",
"source": "mdast-util-mdx-jsx"
}
This isn't really a specific issue with JSFH. A new MDX compatible template could work to resolve this. For now, I'm doing a simple regex replace in my string to strip the leading two newlines in the md_nested template:
Hi,
I'm using this project to generate MDX files from our schema to feed into a Docusaurus static web site for documentation. It seems the
md_nested
template generates non-compliant Markdown with MDX due to mixing inline and newline styles.Here's a snippet that's generated and where the mdx compiler gets upset:
This isn't really a specific issue with JSFH. A new MDX compatible template could work to resolve this. For now, I'm doing a simple regex replace in my string to strip the leading two newlines in the
md_nested
template:The text was updated successfully, but these errors were encountered: