RobertDober
1
RobertDober
Earmark 1.4.18 released
here are the Release Notes:
1.4.18 2021-10-30
-
Updated dependency to EarmarkParser v1.4.17
2
RobertDober
EarmarkParser 1.4.18 released
1.4.18 2021-12-04
-
Deprecate options not useful anymore after the removal of parallel scanning (#72)
-
Do not turn off lookahead on indented fences and check for indent only once (#71)
Kudos to José Valim
-
Add lookahead for fenced code blocks (#70)
- Do lookaheads for fenced code blocks
Prior to this commit, we were trying to parse
all lines between fenced code blocks, which
could be very expensive. Therefore we lookahead
fences and convert them to text.-
Do not scan lines in parallel anymore
-
Remove unused code blocks
-
Handle fenced blocks wrapped in tags
-
Clean up regex
-
More corner cases
-
Optimize text creation
-
Optimize length checks
Kudos to José Valim
0
RobertDober
Here is the compagnon release for Earmark
Earmark 1.4.19 2021-12-04
This release is updating to EarmarkParser v1.4.18 with these RELEASE NOTES
0
derek-zhou
Is there any way to convert an Earmark AST back to markdown? There could be usage cases such as:
- parse an markdown file, do some transformation, and then convert back to markdown
- take a html file, parsed with floki, convert the AST into earmark AST (they looks close enough) and then write out a markdown file
1
al2o3cr
derek-zhou
Thanks. @RobertDober , May I suggest you to take the above mentioned code and merge it into Earmark itself? It is small, useful and more closely related to Earmark than Livebook. Also, you guys obviously already work closely together.
0
josevalim
Creator of Elixir
While the first use case is likely a good idea, I am not sure how useful this case would be in practice:
Markdown is a simple output format, so it may be easier to go from HTML → Markdown, without going through Earmark AST. For example, even if this feature is added to Earmark, we would likely keep our conversion as is instead of introducing an intermediate step. Especially because we only modify the structure of the Markdown document, never the contents of the paragraphs.
0
RobertDober
@derek-zhou
I too fail to see why you would like to manipulate the Earmark AST instead of the Floki AST? I guess reuse of already existing transformation functions might be an argument.
In that case it might perhaps be a good idea to generalize them to work on Floki’s AST instead?
0
RobertDober
and to answer this question: No not right now, of course the meta part of the AST could be used for that but I would hate to load this burden on ex_doc so maybe an Option.
Much work, no time, alas
0