JSON: Add support for merge conflict markers #416
Merged
+314
−0
Conversation
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
deathaxe
force-pushed
the
feat/diff-markers
branch
from
41984a9 to
111e4a0
Compare
keith-hall
approved these changes
Nov 20, 2025
FichteFoll
approved these changes
Nov 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR adds support for merge conflict markers to all JSON based syntaxes, as all of them inherit from dedicated JSON syntax, unrelated to ST's default one.
XML/YAML based onces inherit them from ST core syntaxes and thus don't need changes. Tests are omitted to avoid failures when running CI against ST builds, which do not provide them.