failing test case for commonmark output with Escaped nodes.#680
Open
failing test case for commonmark output with Escaped nodes.#680
Conversation
c755092 to
25e5e8d
Compare
Contributor
Run on Sun Nov 2 06:55:06 UTC 2025 |
578acfd to
99f360b
Compare
8435939 to
d2d0cbb
Compare
8435939 to
fe1dbc1
Compare
99f360b to
d5e4a70
Compare
fe1dbc1 to
c871f8c
Compare
d5e4a70 to
8393821
Compare
c8ec7d3 to
37f0418
Compare
37f0418 to
5b53673
Compare
This file contains hidden or 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
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.
In an input sequence like
\™, withEscapednodes left in (where a user asks for them to be), the CommonMark formatter can't see that&is followed by alpha (since the&is in an isolated node), so it doesn't think it needs escaping.I've given this a few tries, but obvious solutions are not as easy as one would think.