Change order of code block formatting to prevent removal of backticks #301
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.
Description of Change
This adjusts the order of the triple backtick code block formatting so that backticks (`) in the code are preserved.
The
formatCodeContent()
function replaces backticks with their html entities and then the conversion to text viacheerio.text()
reverts them back into backticks. So then, when the single backtick formatter runs it replaces those backticks within the triple backtick code blocks and the disappear from the rendered code block. This prevents that by moving theformatCodeContent()
to after thecheerio.text()
conversion.This also add a backtick example into the triple backtick code block in the
supportedFormats.html
fixture for testing.Related Issue
Fixes #294
Motivation and Context
I recently ran into this issue where backtick in code blocks were disappearing and noticed there was open issue for it.
Checklist
npm run lint
and updated code style accordinglynpm run test
passesrelevant documentation is changed and/or added