Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

commonmark-spec

Package Overview
Dependencies
Maintainers
1
Versions
7
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

commonmark-spec - npm Package Compare versions

Comparing version 0.28.0 to 0.29.0

106

changelog.txt

@@ -0,5 +1,97 @@

[0.29]
* Clarify that entities can't be used to indicate structure (#474).
For example, you can't use `*` instead of `*` for a bullet
list, or `
` to create a new paragraph.
* Limit numerical entities to 6 hex or 7 decimal digits (#487).
This is all that is needed given the upper bound on
unicode code points.
* Specify dropping of initial/final whitespace in setext heading content
(#461).
* Add example with a reference link definition where the reference is never
used (#454).
* Add example with setext header after reference link defs (#395).
* Clarify that script, pre, style close tags can begin an HTML block (#517).
* Remove `meta` from list of block tags in start condition #6 of
HTML blocks (#527). meta tags are used in some inline contexts (though
this isn't valid HTML5), e.g. in schema.org.
* Disallow newlines inside of unquoted attributes (#507,
Shyouhei Urabe) as per HTML spec:
<https://html.spec.whatwg.org/multipage/syntax.html#unquoted>.
* Remove vestigial restriction in list item spec (#543).
The "not separated by more than one blank line" was a left-over
from an earlier version of the spec in which two blank lines
ended a list.
* Fix tests where list items are indented 4+ spaces (#497).
The tests did not accord with the spec here; these
lines should be continuation lines (if no blank space)
or indented code blocks (if blank space).
* Clarify tildes and backticks in info strings (#119).
We disallow backticks in info strings after backtick fences
only. Both backticks and tildes are allowed in info strings
after tilde fences. Add example.
* Indicate that info string is trimmed of all whitespace (#505, Ashe
Connor). As noted in
<https://github.com/github/cmark/issues/60>, the info string
is not only trimmed of "spaces" (U+0020) but also of tabs.
* Don't strip spaces in code span containing only spaces (#569).
This allows one to include a code span with just spaces,
using the most obvious syntax.
* Add example w/ reference link w/ empty destination in `<>` (#172).
* Disallow link destination beginning with `<` unless it is inside `<..>`
(#538). This brings the description in line with the spec example:
```
[foo]: <bar>(baz)
[foo]
.
<p>[foo]: <bar>(baz)</p>
<p>[foo]</p>
```
* Allow spaces inside link destinations in pointy brackets (#503).
This reverts a change in 0.24 and should make things easier
for people working with image paths containing spaces.
* Remove redundant condition. We don't need to specify that the absolute
URI in an autolink doesn't contain `<`, since this is specified in
the description of an absolute URI.
* Add additional spec examples involving link destinations in `<>` (#473).
* Add test for `[test](<url\>)` (#562).
* Disallow unescaped `(` in parenthesized link titles (#526).
* Add example showing need for space before title in reference link (#469).
* Add codepoints for punctuation characters (#564, Christoph Päper).
* Clarify the left- and right-flanking definitions (#534, Jay Martin).
* Match interior delimiter runs if lengths of both are multiples of 3
(#528). This gives better results on `a***b***c` without giving bad
results on the cases that motivated the original multiple of 3 rule.
* Add another test case for emphasis (#509, Michael Howell).
* Code spans: don't collapse interior space (#532).
* Simplify revisions to code span normalization rules.
Remove the complex rule about ignoring newlines adjacent
to spaces. Now newlines are simply converted to spaces.
* Replace image 'url' with 'destination' (#512, Phill).
* Add some links for occurrences of "above" (#480).
* Various typo fixes (#514, Kenta Sato; #533, nikolas;
tnaia, #556; #551, Grahame Grieve).
* Create .gitattributes so that changelog.txt is highlighted as
markdown (#499, Christoph Päper).
* Update GitHub links (Morten Piibeleht).
* Update references to container and leaf block headers to use the
correct pluralization (#531, Elijah Hamovitz).
* Rephrase example #111 to indicate that the rendering is not mandated
(#568).
* Improve documentation of parsing strategy (#563).
Note that `openers_bottom` needs to be indexed to
delimiter run lengths as well as types.
* make_spec.lua: Fix migration of children nodes in create_anchors (#536,
Zhiming Wang). This resulted in some bugs in the rendered spec
(where words would be dropped from links).
* Fix dingus link when double clicking Markdown code (#535, Zhiming Wang).
Prior to this commit, the link opened is always `/dingus/?text=` (no
text).
* Add spec.json generator to Makefile (M Pacer).
[0.28]
* Allow unlimited balanced pairs of parentheses in link URLs
(@kivikakk, jgm/cmark#166). The rationale is that there are many URLs
(@kivikakk, commonmark/cmark#166). The rationale is that there are many URLs
containing unescaped nested parentheses. Note that

@@ -67,3 +159,3 @@ implementations are allowed to impose limits on parentheses

* Add examples for Unicode whitespace (Timothy Gu). In light of
jgm/commonmark.js#107, add a few examples/test cases to make sure the
commonmark/commonmark.js#107, add a few examples/test cases to make sure the
distinction between Unicode whitespace and regular whitespace is kept.

@@ -118,3 +210,3 @@ * Fix missing closing paren typo (Robin Stocker).

* Added several more tab-handling cases (see jgm/cmark#101).
* Added several more tab-handling cases (see commonmark/cmark#101).
* Fixed spec test for tabs. In the blockquote with a tab following

@@ -248,3 +340,3 @@ the `>`, only one space should be consumed, yielding two spaces

* Added test case clarifying laziness in block quotes (see
jgm/commonmark.js#60).
commonmark/commonmark.js#60).
* Add an example with mixed indentation code block in "Tabs" section

@@ -301,10 +393,10 @@ (Robin Stocker). This makes sure that implementations skip columns instead

* Added test for edge case in link reference parsing
(Benjamin Dumke-von der Ehe, see jgm/commonmark.js#49).
(Benjamin Dumke-von der Ehe, see commonmark/commonmark.js#49).
* Added link tests with fragment identifiers and queries (David
Green, #342).
* Added test cases with a literal backslash in a link destination
(see jgm/commonmark.js#45).
(see commonmark/commonmark.js#45).
* Added test for entity `&ngE;` which resolves to two code points.
Put entity tests on several lines for readability (see
jgm/commonmark.js#47).
commonmark/commonmark.js#47).
* Fixed broken "pre" literal HTML example. Contents

@@ -311,0 +403,0 @@ weren't escaped properly.

4

package.json
{
"name": "commonmark-spec",
"version": "0.28.0",
"version": "0.29.0",
"description": "CommonMark spec and test cases",

@@ -11,3 +11,3 @@ "homepage": "http://commonmark.org",

],
"repository": "jgm/CommonMark",
"repository": "commonmark/CommonMark",
"license": "MIT",

@@ -14,0 +14,0 @@ "files": [

@@ -20,8 +20,8 @@ CommonMark

- <https://github.com/jgm/cmark> (C)
- <https://github.com/jgm/commonmark.js> (JavaScript)
- <https://github.com/commonmark/cmark> (C)
- <https://github.com/commonmark/commonmark.js> (JavaScript)
There is a list of third-party libraries
in a dozen different languages
[here](https://github.com/jgm/CommonMark/wiki/List-of-CommonMark-Implementations).
[here](https://github.com/commonmark/CommonMark/wiki/List-of-CommonMark-Implementations).

@@ -116,3 +116,3 @@ Running tests against the spec

inside HTML block-level tags, if you want to, but also allows you to
exclude this. It is also makes parsing much easier, avoiding
exclude this. It also makes parsing much easier, avoiding
expensive backtracking.

@@ -141,7 +141,2 @@

- The spec stipulates that two blank lines break out of all list
contexts. This is an attempt to deal with issues that often come up
when someone wants to have two adjacent lists, or a list followed by
an indented code block.
- Changing bullet characters, or changing from bullets to numbers or

@@ -166,3 +161,3 @@ vice versa, starts a new list. We think that is almost always going

github issues for questions and possibly open-ended discussions.
Use the [github issue tracker](http://github.com/jgm/CommonMark/issues)
Use the [github issue tracker](http://github.com/commonmark/CommonMark/issues)
only for simple, clear, actionable issues.

@@ -169,0 +164,0 @@

Sorry, the diff of this file is too big to display

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc