fix: a whole bunch of < where < should be#264
Closed
KernelDeimos wants to merge 1 commit intojsdoc:mainfrom
Closed
fix: a whole bunch of < where < should be#264KernelDeimos wants to merge 1 commit intojsdoc:mainfrom
< where < should be#264KernelDeimos wants to merge 1 commit intojsdoc:mainfrom
Conversation
On multiple markdown pages there were HTML-escaped `<` characters when it was clear that the literal character was intended. This results in the documentation pages showing `<` in the browser where `<` is what is meant to be shown, which happens because markdown already HTML-escapes special characters seen in code blocks. It is suspected (by me) that a previous markdown renderer with a bug was used and using `<` in place of `<` was a workaround, then later the markdown previewer used was changed and nobody noticed this issue.
Author
|
Merge #259 instead |
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.
Fixes #263
On multiple markdown pages there were HTML-escaped
<characters when it was clear that the literal character was intended. This results in the documentation pages showing<in the browser where<is what is meant to be shown, which happens because markdown already HTML-escapes special characters seen in code blocks.It is suspected (by me) that a previous markdown renderer with a bug was used and using
<in place of<was a workaround, then later the markdown previewer used was changed and nobody noticed this issue.