Repository navigation
Remove houdini unescape html - #652
Merged
Merged
Conversation
Add a boolean parameter to cmark_unescape_string that controls whether backslash-escapes are recognized. (They are not inside autolinks, which is why the houdini functions were still used.)
These are no longer used.
Contributor
|
LGTM |
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.
This follows up on #650 by removing houdini_unescape_html functions.
To do this, I needed to add a parameter to cmark_unescape_string that determines whether backslash escapes are recognized. Otherwise, the houdini functions would still have been needed for autolinks, which don't recognize backslash escapes.