Thanks for the advice. Stealing the above cited Livebook code and retrofiting it onto Floki AST shall satisfy my immediate need. I asked to see if there is any grand plan in place already.
derek-zhou
RobertDober
RobertDober
Happy New Year
I just released a quickfix release for EarmarkParser v1.4.19
1.4.19 2022-01-07
-
Footnotes fixed and upgraded(#26)
Footnotes are now a superset of GFM Footnotes. This implies some changes
- Footnote definitions (
[^footnote_id]) must come at the end of your document (GFM) - Footnotes that are not referenced are not rendered anymore (GFM) - Footnote definitions can contain any markup with the exception of footnote definitions
- Footnote definitions (
N.B.
Footnotes are not downwards compatible with 1.4.18 and therefore no accompaning Earmark Release will be done (ex_doc does not use footnotes)
hopefully 1.5.0 will come out soon with breaking list changes too
1
RobertDober
I appologize to all Earmark users I forgot that the incompatible release of EarmarkParser will cause problems on Earmark
please upgrade to 1.4.20 which assures the usage of the compatible EarmarkParser version 1.4.18
Earmark 1.4.20 2022-01-08
- Fix EarmarkParser version to 1.4.18 as the 1.4.x branch is not supporting Earmark anymore (1.5 should hopefully)
0
RobertDober
Erratum on EarmarkParser Release Note
1.4.19 2022-01-07
-
Fix stop condition on closing HTML in scanners lookup algo
Kudos to José Valim
-
Footnotes fixed and upgraded(#26)
Footnotes are now a superset of GFM Footnotes. This implies some changes
- Footnote definitions (
[^footnote_id]) must come at the end of your document (GFM) - Footnotes that are not referenced are not rendered anymore (GFM)
- Footnote definitions can contain any markup with the exception of footnote definitions
- Footnote definitions (
1
RobertDober
Earmark Parser 1.4.20 released
Synopsis
(although the original Synapsis deserves to be conserved)
This drops support for Elixir 1.10 and incorporates some small changes for the new admonition support for ex_doc which have been gracefully provided by @josevalim
1.4.20 2022-02-21
-
Preserve newlines inside HTML code
Kudos to José Valim
-
Do not remove ial on blockquote inside triple quoted
Kudos to José Valim
-
Removed support for Elixir 1.10 (following
ex_doc’s lead)
1
RobertDober
# Earmark 1.4.21 release delayed
Earmark 1.5.0-pre released
1.5.0-pre 2022-02-21
This introduces regressions concerning nested lists and sophisticated edge cases, but introduces the following features as well as all features of EarmarkParser 1.4.19 & 1.4.20
The will be regressions fixed in 1.5.0
-
Removing support for Elixir < 1.12
-
Bad link corrected
Kudos to Udo Kramer -
Nice addition to
Earmark.Transform.transformto allow modification of the content of an AST node
Kudos to Phillipp Tessenow
1
RobertDober
I just released a hotfix for missing paragraph context after indented code blocks Alternative header syntax after code is "invalid" · Issue #98 · RobertDober/earmark_parser · GitHub
All three links are the same, sorry
EarmarkParser Release 1.4.21 2022-03-13
Earmark Release 1.5.0-pre1 2022-03-13
2
RobertDober
I just released
EarmarkParser 1.4.22
and
Earmark 1.4.21
EarmarkParser 1.4.22 fixes the list regressions (as 1.5 will just not be ready soon)
and thus Earmark can be used with ex_doc again (c.f. Hopefully this shall take care of the issue reported here by RobertDober · Pull Request #29 · surface-ui/surface_catalogue · GitHub)
For completeness the somehow redundant RELEASE NOTES
EarmarkParser
1.4.22 2022-03-14
Fixes all List Regressions introduced in 1.4.19
GFM support for lists remain limited (spaced and tight lists are not 100% compliant) but is better than in 1.4.18
Earmark
1.4.21 2022-03-14
Takes advantage of the fixed regressions in EarmarkParser release 1.4.22 and therefore makes all
features of the latest EarmarkParser release available
2
RobertDober
I just fixed two other regressions in lists in this release
Earmark 1.4.23 2022-03-16
Two more list regressions fixed
-
multi line inline code was ignored in the body parts of lists
-
spaced lists with inline code in their bodies (single and multiline) were rendered tightly (no surrounding
<p>...</p> -
oh and a lot of dead code elimination and a 98% code coverage
Earmark 1.4.22 2022-03-16
1