Skip to content

Releases: tc39/ecmarkup

Version 17.1.1

03 Aug 20:57
Compare
Choose a tag to compare

make redeclaration rule slightly more strict d9df38b

Version 17.1.0

03 Aug 20:47
Compare
Choose a tag to compare
  • lint for redeclarations in #541

Version 17.0.2

03 Jul 20:59
Compare
Choose a tag to compare
  • prevent line wrap at end of Records and Lists in #535
  • fix "there exists"/"such that" not followed by a var name in #538

Version 17.0.1

18 Jun 21:12
Compare
Choose a tag to compare
  • ecma coc anchor in #525
  • better heuristic for determining active clause in #526
  • Initialize to a reasonable amount of TOC expansion in #512
  • Fix <ins>/<del> with structured headers in #533

Version 17.0.0

20 Apr 19:19
Compare
Choose a tag to compare

What's Changed

New on-by-default lint rule: consistency in multiline vs single-line "if" and "else" (#524)

Version 16.2.0

07 Apr 01:50
Compare
Choose a tag to compare

What's Changed

  • support marking individual steps as legacy/optional/deprecated in #523

Version 16.1.1

16 Feb 17:53
Compare
Choose a tag to compare

This fixes a bug in the formatter introduced in the previous release.

Version 16.1.0

15 Feb 07:42
Compare
Choose a tag to compare

The primary feature of this version (by pulling in tc39/ecmarkdown#96) is that now you can click [[FieldNames]] to highlight other uses of those names within the current algorithm, as already happens for variable names.

Also the variable use/def rule should now work better in the presence of <ins>/<del> tags.

Version 16.0.1

25 Jan 20:20
Compare
Choose a tag to compare

What's Changed

  • Fix some minor issues and inconsistencies in string handling in #501
  • Match synthesized selectable counter markers to the context list in #504
  • Exempt script and style element contents from inspection in #511
  • "one of" is an alias for "either" in #514

Version 16.0.0

27 Nov 18:28
Compare
Choose a tag to compare

The breaking change is

  • remove special treatment of "the result of evaluating" in #497

This is only relevant to documents using mark-effects, and is unlikely to affect specifications other than ecma-262 (which will require a small tweak to manually annotate the last remaining two uses of that phrase).

Also includes

  • rephrase algorithm lint rules in terms of parsed lines in #498