-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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 backticks in inline code (replaces #503, fixes #312) #1013
Conversation
@@ -664,7 +664,7 @@ InlineLexer.prototype.output = function(src) { | |||
// code | |||
if (cap = this.rules.code.exec(src)) { | |||
src = src.substring(cap[0].length); | |||
out += this.renderer.codespan(escape(cap[2].trim(), true)); | |||
out += this.renderer.codespan(escape(cap[3].trim(), true)); |
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.
@Feder1co5oave @joshbruce We have to watch out for changing capturing parentheses. This can be a breaking change. https://github.com/firede/msee/pull/59/files
They actually re-wrote the parser, while using its internal regex rules, so I maintain this should not be considered a breaking change as suggested in #1059 |
revert number of capturing parens in #1013
fix backticks in inline code (replaces markedjs#503, fixes markedjs#312)
revert number of capturing parens in markedjs#1013
Fixes #312:
Tests are about checking for whitespace, which is ignored by our test system for now.