Introduce mark operation to Text.setStyle #643
Draft
Conversation
This file contains 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
hackerwins
force-pushed
the
main
branch
3 times, most recently
from
7892142 to
fdc2e1c
Compare
hackerwins
force-pushed
the
main
branch
2 times, most recently
from
fbc6098 to
7d65a57
Compare
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.
What this PR does / why we need it:
Currently, the
Text.setStylelogic sometimes doesn't adequately preserve user intent when formatting text concurrently. Therefore, we have introduced the mark operation of the Peritext algorithm toText, enabling the reflection of user intent in concurrent editing scenarios.This implementation is currently being worked on in the PR#647, and this PR just updated the protocol for the purpose of concurrent testing.
Which issue(s) this PR fixes:
Address #672
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Additional documentation:
Checklist: