-
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
revert number of capturing parens in #1013 #1060
Conversation
+1, thanks This looks more commonmark compliant too (they don't require that leading and trailing spaces match) |
lib/marked.js
Outdated
@@ -468,7 +468,7 @@ var inline = { | |||
nolink: /^!?\[((?:\[[^\]]*\]|\\[\[\]]|[^\[\]])*)\]/, | |||
strong: /^__([\s\S]+?)__(?!_)|^\*\*([\s\S]+?)\*\*(?!\*)/, | |||
em: /^_([^\s_](?:[^_]|__)+?[^\s_])_\b|^\*((?:\*\*|[^*])+?)\*(?!\*)/, | |||
code: /^(`+)(\s*)([\s\S]*?[^`]?)\2\1(?!`)/, | |||
code: /^(`+)(?:\s*)([\s\S]*?[^`]?)(?:\s*)\1(?!`)/, |
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.
There's no need to capture then!
/^(`+)\s*([\s\S]*?[^`]?)\s*\1(?!`)/
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.
good catch
This is a merge + publish (0.3.15), yeah? If so, makes me think we should have another owner who can publish...I’m at dinner, but if one of y’all could publish, we could increase our flow rate for hot-fix type things. Thoughts?? |
yeah, merge + publish I would be ok with more permission. |
@UziTech @Feder1co5oave - Any tests we can write to guard against future regression?? (Really looking forward to the CI thing.) Publishing |
Is anyone working on setting up CI? Maybe that's something I can help with. |
It's been set up in #1020, head over there and give us some advice if you
wish!
|
revert number of capturing parens in markedjs#1013
This reverts the number of capturing parentheses in
inline.code
grammar from #1013The regex should still function the same.
fixes #1059