-
Notifications
You must be signed in to change notification settings - Fork 367
fix: preserve template delimiters inside fenced code blocks in safe-output sanitizer #28736
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+729
−78
Merged
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
5059ec3
Initial plan
Copilot 0d9457a
fix: preserve template delimiters inside fenced code blocks in safe-o…
Copilot fe01828
fix: remove typeof core checks from neutralizeTemplateDelimiters
Copilot f9cf5e1
test: add extensive unit + fuzz tests for parser (getFencedCodeRanges…
Copilot f8a9047
fix: address all PR review comments on parser tests and core guards
Copilot fd30d3e
fix: remove all typeof core guards from sanitize_content_core.cjs
Copilot b8ae0f0
fix: add global.core setup to sanitize_title.test.cjs
Copilot d371126
Merge branch 'main' into copilot/fix-safe-output-sanitizer
pelikhan File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
neutralizeTemplateDelimitersnow callscore.info/core.warningunconditionally. This will throw a ReferenceError ifcoreis not present in the global scope (e.g., when importingsanitize_content_core.cjsin a plain Node context withoutsetupGlobals()/shim.cjs). Other functions in this file still guardcoreaccess viatypeof core !== "undefined", so this introduces an inconsistency and a potential runtime regression when template patterns are present. Consider restoring thetypeof core !== "undefined" && core.*guards here, or consistently referencingglobal.corewith a safe fallback/no-op logger.