Server front-end: do not apply Markdown formatting in code sections #6850
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 modifies the rules for "Markdownish" formatting in the server's front-end to only replace formatting characters (like '_' and '*') and headings outside of code sections.
This keeps the formatter from messing up Python comments (
# comment
) and function names with underscores in code examples (my_example_function()
).The idea of the regex follows the accepted answer here: https://stackoverflow.com/questions/6462578/regex-to-match-all-instances-not-inside-quotes - only perform the replacement if it is followed by an even number of backquotes. This is still not perfect for truncated or invalid Markdown, and it only applies the correct formatting once the code section is closed, but at least it fixes some straightforward cases of code rendering.