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.
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
Follow GFM spec on EM and STRONG delimiters #1686
Follow GFM spec on EM and STRONG delimiters #1686
Changes from 8 commits
40493bb
4e2ec90
283ab9c
c38ee23
7c6551e
bc17ded
ea203cf
556070b
4cbba07
335a660
e926e0c
c60c9ba
54218fe
2a45677
d233fd5
56b6f5e
4db32dc
4e7902e
bd4f8c4
211b9f9
cc778ad
226bbe7
1fb141d
ad720c1
e27e6f9
6b729ed
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Are you sure you want to remove these tests?
It looks like @UziTech added these in PR #1181.
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.
They do not confirm to the commonmark spec, so trying to get them to pass was counterproductive.
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.
Maybe we can update the output of these two tests to match commonmark's output:
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.
We could... but this PR does not parse it correctly either. This is essentially Commonmark Example 442 in the test files, which we currently do not pass.
Since it wasn't correct in the earlier version, I feel it would be OK to let this one slide for now (this PR isn't breaking 442 or causing any regressions on things that worked correctly), and work on fixing that test in a future development. Getting this one obscure test to work that wasn't even working before involves some obnoxious workarounds and I don't know if it's worth focusing on it for this PR. Once this is stable I plan to go over more failing test cases and I can start tackling that one.
I hope that makes sense where I'm coming from.
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.
Yep that makes sense. I think this corner case will probably affect very few people so it can be addressed in a different PR 👍