Markdown: Workaround for double wrap hook#2719
Merged
RunDevelopment merged 1 commit intoPrismJS:masterfrom Jan 29, 2021
Merged
Conversation
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
1 participant
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 is a workaround for #2716.
The problem in #2716 is that Markdown's
wraphook function might be added multiple times because the language might be reloaded. I did not account for that when writing the function, so this is a fix for that. However, it does not solve the underlying issue.This workaround should be kept even after #2716 was fixed because other plugins might modify
env.contentbefore Markdown and add custom HTML.