Consider using a React component instead of diff2html for patch preview - #6883
Open
goldpanth3r wants to merge 1 commit into
Conversation
goldpanth3r
force-pushed
the
fix-6868-Consider-using-a-React-component-instead-of-diff2html-for-patch-preview
branch
from
September 21, 2026 06:12
a75d708 to
2175760
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
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 #6868
Replaced diff2html's dangerouslySetInnerHTML-based rendering in PatchView with react-diff-view, which renders the diff as real React elements instead of an injected HTML string.
(replacing diff2html's drawFileList option)
(--green/--red at the same opacity used by .badge.succeeded/.failed),
added in globals.css
(replacing diff2html's colorScheme: ColorSchemeType.DARK)