Releases: quantizor/markdown-to-jsx
v7.6.0
Minor Changes
-
2281a4d: Add
options.disableAutoLink
to customize bare URL handling behavior.By default, bare URLs in the markdown document will be converted into an anchor tag. This behavior can be disabled if desired.
<Markdown options={{ disableAutoLink: true }}> The URL https://quantizor.dev will not be rendered as an anchor tag. </Markdown> // or compiler( 'The URL https://quantizor.dev will not be rendered as an anchor tag.', { disableAutoLink: true } ) // renders: <span> The URL https://quantizor.dev will not be rendered as an anchor tag. </span>
Patch Changes
- fb3d716: Simplify handling of fallback scenario if a link reference is missing its corresponding footnote.
v7.5.1
v7.5.0
Minor Changes
-
62a16f3: Allow modifying HTML attribute sanitization when
options.sanitizer
is passed by the composer.By default a lightweight URL sanitizer function is provided to avoid common attack vectors that might be placed into the
href
of an anchor tag, for example. The sanitizer receives the input, the HTML tag being targeted, and the attribute name. The original function is available as a library export calledsanitizer
.This can be overridden and replaced with a custom sanitizer if desired via
options.sanitizer
:// sanitizer in this situation would receive: // ('javascript:alert("foo")', 'a', 'href') <Markdown options={{ sanitizer: (value, tag, attribute) => value }}> {`[foo](javascript:alert("foo"))`} </Markdown> // or compiler('[foo](javascript:alert("foo"))', { sanitizer: (value, tag, attribute) => value, })
Patch Changes
- 553a175: Replace RuleType enum with an object
v7.4.7
Patch Changes
- 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 🤝
v7.4.6
Patch Changes
-
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; } }}
v7.4.5
Patch Changes
-
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.
v7.4.4
What's Changed
- Brackets in link text by @zegl in #551
- Multiline footnotes by @zegl in #553
- fix: multi-line emphasis by @austingreco in #550
- fix: gracefully handle missing image references by @quantizor in #554
- chore: add changesets by @quantizor in #555
- fix: handle newlines inside HTML tag brackets by @quantizor in #557
- fix: html block regex prefix conflict by @quantizor in #558
- Version Packages by @github-actions in #556
New Contributors
- @zegl made their first contribution in #551
- @austingreco made their first contribution in #550
- @github-actions made their first contribution in #556
Full Changelog: v7.4.3...v7.4.4