Unified merge view - improve what text is in cm-deletedText

[ondrejmirtes]

Describe the issue

Hello,
I'm really grateful that CM6 includes unifiedMergeView. When I started a project that needs it, I had no idea whether I'll have to spend several days implementing my own (inferior) solution, but fortunately I found @codemirror/merge.

I have a suggestion: in the diff like this:

I'd like if -next-line part of the deleted line was inside cm-deletedText so that it'd also be highlighted similarly to identical.alwaysFalse, booleanAnd.alwaysFalse part of the added line.

This is currently how the DOM looks like:

<div class="cm-deletedChunk" contenteditable="false"><del>				/** @phpstan-ignore-next-line */</del><span class=" cm-deletedText"></span></div>
<div class="cm-changedLine cm-line"><ins class="cm-insertedLine">				<span class="ͼy">/** @phpstan-ignore</span><span class="cm-changedText"><span class="ͼy"> identical.alwaysFalse, booleanAnd.alwaysFalse</span></span><span class="ͼy"> */</span></ins></div>

I'd prefer if it looked something like this:

<div class="cm-deletedChunk" contenteditable="false"><del>				<span class="ͼy">/** @phpstan-ignore</span><span class=" cm-deletedText"><span class="ͼy">-next-line</span></span><span class="ͼy"> */</span></del></span></div>
<div class="cm-changedLine cm-line"><ins class="cm-insertedLine">				<span class="ͼy">/** @phpstan-ignore</span><span class="cm-changedText"><span class="ͼy"> identical.alwaysFalse, booleanAnd.alwaysFalse</span></span><span class="ͼy"> */</span></ins></div>

Thank you for considering this.

Browser and platform

No response

Reproduction link

No response

[marijnh]

Deleted text is highlighted. I'm not sure how that screenshot was made, it seems to use different styling than the default (compare). Maybe some mistake was made in the custom styles?

[ondrejmirtes]

Yeah, I have custom styles but without them it still doesn't work. It can't because the current DOM is not structured for that.

This is how it looks with the default styles:

[marijnh]

Oh, right, unified view, I was looking at the split merge view. That indeed doesn't seem to render changed spans separately.

[ondrejmirtes]

Here's a reproduction on /try/.

[ondrejmirtes]

One unrelated question: how can I expect getChunks(state) to look in the unified merge view? Do they always have side set to 'b'? It seems like that from my testing (I don't know what text should I produce in order to have some chunks on side 'a'). Thanks.

[marijnh]

side is a per-editor thing that tells you which side of the chunks represent the document in that editor. In a split merge view both editors have a different side. In a unified view the editor is always b, and a refers to the given original document.