-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Fix/em yo #1654
Fix/em yo #1654
Conversation
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/markedjs/markedjs/2i2a4afnt |
test/specs/gfm/commonmark.0.29.json
Outdated
@@ -2850,7 +2850,7 @@ | |||
}, | |||
{ | |||
"markdown": "a*\"foo\"*\n", | |||
"html": "<p>a*"foo"*</p>\n", | |||
"html": "<p>a<em>"foo"</em></p>\n", |
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.
according to the commonmark spec that should not change.
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.
These common mark tests are derived from the spec so they should not be changed unless a new version of the spec comes out.
If a spec is marked with shouldFail: true
that means it is failing and needs to be fixed in marked.
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.
marked as shouldFail
Seems like this is moving backwards in spec compliance. Could you find a way to fix |
I don't really understand
|
The problem is that https://spec.commonmark.org/dingus/?text=a*%22Yo%22* is not working correctly with this PR but it is working without this PR. |
Can you find a way to make It will probably involve editing the |
To do this, just return the rule to the state of the master, but then this PR has no value |
|
Can you update this PR to make both work with this PR? |
no since it is one and the same this solution will work for |
It is definitely possible. You will have to change more than just the I don't think this PR should be merged if it could break current spec compliant markdown. |
Description
Contributor
Committer
In most cases, this should be a different person than the contributor.