- 7603248: Fix parsing isolation of individual table cells.
- f9328cc: Improved block html detection regex to handle certain edge cases that cause extreme slowness. Thank you @devbrains-com for the basis for this fix 馃
-
a9e5276: Browsers assign element with
id
to the global scope using the value as the variable name. E.g.:<h1 id="analytics">
can be referenced viawindow.analytics
. This can be a problem when a name conflict happens. For instance, pages that expectanalytics.push()
to be a function will stop working if the an element with anid
ofanalytics
exists in the page.In this change, we export the
slugify
function so that users can easily augment it. This can be used to avoid variable name conflicts by giving the element a differentid
.import { slugify } from 'markdown-to-jsx'; options={{ slugify: str => { let result = slugify(str) return result ? '-' + str : result; } }}
-
f5a0079: fix: double newline between consecutive blockquote syntax creates separate blockquotes
Previously, for consecutive blockquotes they were rendered as one:
Input
> Block A.1 > Block A.2 > Block B.1
Output
<blockquote> <p>Block A.1</p> <p>Block A.2</p> <p>Block.B.1</p> </blockquote>
This is not compliant with the GFM spec which states that consecutive blocks should be created if there is a blank line between them.
- 8eb8a13: Handle newlines inside of HTML tags themselves (not just nested children.)
- c72dd31: Default
children
to an empty string if no content is passed. - 4f752c8: Fix handling of deeply-nested HTML in some scenarios.
- 1486aa4: Handle extra brackets in links, thanks @zegl!
- 1486aa4: Allow a newline to appear within inline formatting like bold, emphasis, etc, thanks @austingreco!
- 1486aa4: Starting using changesets
- fd35402: Fix HTML block regex for custom component scenarios where a nested component shares the same prefix as the parent, e.g. Accordion vs AccordionItem.
- 1486aa4: Fix support for multi-line footnotes, thanks @zegl!