Escape rule and schema text in the site's reference pages - #22
Merged
Merged
Conversation
The generator writes catalog and schema text into Markdown that mdBook renders as HTML, so markup characters are escaped; today's pages are unchanged.
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.
The release self-check flags
site/generate.pyfor writing text into pages unescaped. Its input is JevGate's own catalog and schema, but escaping markup characters costs nothing and keeps a future<or&in a rule's text from rendering as HTML. The generated pages are byte-identical today. (The same change is part of #18, which is open for review; this lands it without waiting.)