Skip to content

Split merge comment ranges#2410

Merged
tf merged 5 commits intocodevise:masterfrom
tf:split-merge-comment-ranges
Apr 28, 2026
Merged

Split merge comment ranges#2410
tf merged 5 commits intocodevise:masterfrom
tf:split-merge-comment-ranges

Conversation

@tf
Copy link
Copy Markdown
Member

@tf tf commented Apr 28, 2026

REDMINE-21261

tf added 5 commits April 28, 2026 13:14
Structural ops that go through `Batch` (split, maybeMerge) now
carry comment thread range updates and subject_id migrations
alongside the configuration changes. Move, delete and insert pass
their `reviewSession` to Batch, which threads the resulting
per-thread range shifts and target-element migrations into both
the wire payload (`comment_thread_subject_ranges`,
`migrate_comment_threads`) and the post-save `ReviewSession` state.

Keeps thread highlights anchored to their characters as users
insert, delete or move content elements between text blocks.

REDMINE-21261
When the EditableText value is replaced externally — e.g. after a
textBlock split or merge that migrated comment ranges through Batch
— the live rangeRefs were anchored to the previous content,
producing stale or missing highlights for one render. Reset them as
the new value lands and let the post-render effect rebuild them
against the new content.

REDMINE-21261
@tf tf added this to the v17.2 milestone Apr 28, 2026
@tf tf merged commit 935ffec into codevise:master Apr 28, 2026
18 checks passed
@tf tf deleted the split-merge-comment-ranges branch April 28, 2026 12:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant