-
Notifications
You must be signed in to change notification settings - Fork 12
Merge commonmark@0.31.2 #22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
This reverts commit 4082a18.
This reverts commit 3ea1589.
Unclosed (potential) link titles containing lots of consecutive underscores caused an exponential slowdown. Thanks to Stefan Dobre for reporting.
According to the specification, blank lines in a block quote doesn't separate list items: https://spec.commonmark.org/0.30/#example-320 Therefore, the following example should be tight: - > - a > - b The specification also say that link reference definitions can be children of list items when checking list tightness: https://spec.commonmark.org/0.30/#example-317 Therefore, the following example should be loose: - [aaa]: / [bbb]: / - b This commit fixes those problems with the following strategy: - Using source end position and start position of adjoining elements to check tightness. This requires adjusting source end position of some block types to exclude trailing blank lines. - Delaying removal of link reference definitions until the entire document is parsed.
The reasoning that a failed delimiter means future delimiters will also fail only applies if the reason they failed was not the multiple-of-three rule. This was already implemented correctly for asterisks, but not for underscore.
if the info string already starts with `language-`. Closes commonmark#277.
This updates the library to conform to the 0.31 spec.
A spec 0.31 change we forgot in last release.
`trim()` as previously defined could take a long time on very long strings.
|
I tested this locally, and have also kicked off Detox tests via mattermost/mattermost-mobile#8722. |
enahum
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lgtm
|
@hmhealey, with mattermost/mattermost-mobile#8722 passing on this commit, what's the process after merging to publish to NPM? |
I think I just did it manually by building the package locally, doing a dry run publish ( |
Summary
Merge @0.31.2.
Ticket Link
Relates-to: https://mattermost.atlassian.net/browse/MM-63537