Releases: tc39/ecmarkdown
Releases · tc39/ecmarkdown
3.0.6
3.0.5
Fixed an issue where a single line break was not properly converted to a space when the beginning of the next line contained a formatting character. For example,
blah blah blah
~Atomics~ foo bar baz
used to become blah blah blah<emu-const>Atomics</emu-const> foo bar baz
, but now becomes blah blah blah <emu-const>Atomics</emu-const> foo bar baz
.
3.0.4
Fixed several bugs regarding paragraph break parsing:
- Parsing fragments that contained paragraph breaks would only emit the first paragraph. Now all paragraphs are joined with a space, i.e., the
\n\n
is collapsed into - Parsing documents with leading whitespace would cause odd behavior.
- Parsing documents that contain paragraph breaks would concatenate them all into a single paragraph. Now they properly split as separate paragraphs. (However, we still don't have full "Markdown-style" paragraph processing, in that if you start a line with a HTML tag, it will still always be wrapped in a paragraph.)
3.0.3
3.0.2
3.0.1
3.0.0
This release brought on @bterlson as a contributor, as he rewrote the parser to be hand-rolled instead of generated, adding much speed and flexiblity. Thanks to Brian for all of the changes listed here!
Changes to the Ecmarkdown language
- Added unordered lists.
- Added backslash escaping.
- Removed the string production (i.e. the auto-
<code>
-ification of strings). - Changed the parsing of variable syntax to better match existing usage and conflict less with idiomatic underscore usage.
- Changed many edge-case behaviors, generally to be more sane.
Changes to the API
- Added a
document
export, which allows as input sequence of paragraphs and lists. - Removed the
list
export.
Changes to the output
- The output is no longer beautified, as this was found to slow down performance by multiple orders of magnitude, and was probably unnecessary anyway since beautification is better done on a whole-document level.
- The exact positioning of HTML comments in the output has changed for a given input, e.g. they now appear inside
<li>
s instead of in between them.