Merge 0.11 branch #886
Closed
Merge 0.11 branch #886
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We want to normalize links if they're utf8, but with something like `[x](%DD)`, leave them as-is.
commonmark_js fuzz: fix spurious failure with non-utf8 link
This is a follow-up of #856, because that pull request didn't cover the case where the URL mixed punctuation and non-utf8 bytes.
commonmark_js fuzz: fix spurious failure with mixed link
That would be ambiguous, because it can't easily be distinguished between the block quote `>` and the end of an HTML tag `>`. If this function bails out because it can't find an `=`, it should point at the spot immedatiely after the attribute name instead.
…nfusion Don't exit `scan_attribute` with the ix pointing at block quote
This changes the interpretation of this document:
````markdown
```
```
````
Without this fix, pulldown-cmark thinks the second line has three
spaces of indentation, and is a valid closing code fence.
Most other commonmark implementations interpret it as having four,
because they start counting at the beginning of the line instead
of the opening fence's indentation level.
Check indentation on the closing fence relative to the line
Document `LineStart` tab handling.
Adjust documentation on custom attributes
Adjust strikethrough flanking rule to better fit Rustdoc Crater run
…that is published to crates.io
Add symlink to license file so it is included in the release tarball that is published to crates.io
perf: cargo-wizard default recommendations for runtime perf
fix: fix dead code warning from nightly compiler
Eat all spaces after line break in link title
Mark `Rule` as a block item
`self.write` sets `self.end_newline = false`: https://github.com/tomcur/pulldown-cmark/blob/de575f0f328eaf574fd747c8510ce98012a05ddd/pulldown-cmark/src/html.rs#L86-L88
fix: remove unnecessary end_newline set
|
Closed because wrong direction 😓 . |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The development has been slowed down a bit, so let's create the 0.11 release and left description lists and the more polished #881 for the 0.12 version.