Repository navigation
docs: clarify escaping with Parser filters - #10594
Merged
michalsn merged 1 commit intoOct 1, 2026
Merged
Conversation
carson-codeigniter4
Bot
added
the
documentation
datamweb
approved these changes
Oct 1, 2026
paulbalandan
approved these changes
Oct 1, 2026
michalsn
force-pushed
the
docs/parser-filter-escaping
branch
from
October 1, 2026 13:56
aa77517 to
ab69702
Compare
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
3 participants
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
This PR clarifies that the Parser does not add
escautomatically when a substitution uses filters, consistent with existing Parser tests that expect HTML output from filters such asnl2brandhighlight. Adds examples of where to placeescand notes that unknown filters are ignored.Checklist: