feat(web): add helper for tokenizing Transform.insert via tokenization of applied context 🚂 #14805
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
User Test ResultsTest specification and instructions User tests are not required Test Artifacts
|
keymanapp-test-bot
bot
changed the title
jahorton
force-pushed
the
feat/web/backward-slide-tokenization
branch
from
8ca53ed to
b1d3899
Compare
…n of applied context Relates-to: #14679 Build-bot: skip build:web Test-bot: skip
jahorton
force-pushed
the
feat/web/trace-insert-edits
branch
from
602d212 to
9ffc093
Compare
ermshiperete
approved these changes
Oct 1, 2025
Base automatically changed from
feat/web/backward-slide-tokenization
to
epic/autocorrect
October 6, 2025 14:51
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 a method that can determine which parts of a
Transform's.insertcomponent landed within each post-application "token" of the context.When updating our context state information in order to attempt reuse of prior calculations, we need to know where the input's components align with them so that they affect the predictive-text process correctly.
Note that the
.deleteLeftcomponent is instead determined when building the edge window, as it takes effect on the original state and tokenization of the context. (Of particular note here: if a token is fully deleted, there's no reason to preserve it - we can delete it instead [or replace it, if new text is set in the same place].)Relates-to: #14679
Build-bot: skip build:web
Test-bot: skip