change(web): simplify mapWhitespacedTokenization requirements 🚂#15919
Draft
jahorton wants to merge 1 commit into
Draft
Conversation
User Test ResultsTest specification and instructions User tests are not required |
keymanapp-test-bot
Bot
changed the title
jahorton
force-pushed
the
feat/web/multi-token-predict-core
branch
from
6d11477 to
fdd65c0
Compare
jahorton
force-pushed
the
change/web/abstract-whitespace-tokenization-mapping
branch
from
7539b3e to
6c1170d
Compare
jahorton
force-pushed
the
change/web/abstract-whitespace-tokenization-mapping
branch
from
da7359e to
a800a12
Compare
jahorton
changed the base branch from
feat/web/multi-token-predict-core
to
change/web/simplify-predict-calls
jahorton
force-pushed
the
change/web/abstract-whitespace-tokenization-mapping
branch
2 times, most recently
from
c12cef9 to
5f4d1ee
Compare
jahorton
changed the base branch from
change/web/simplify-predict-calls
to
refactor/web/expose-suggestion-root-tokenization
jahorton
force-pushed
the
refactor/web/expose-suggestion-root-tokenization
branch
from
3227268 to
1368431
Compare
To better handle inputs that shift the word-boundary in some custom models and models released before Keyman 14.0, this PR provides generalized re-use of the whitespace-based token-transition algorithm used for our most prominently-supported models. Build-bot: skip build:web Test-bot: skip
jahorton
force-pushed
the
change/web/abstract-whitespace-tokenization-mapping
branch
from
5f4d1ee to
7eb3030
Compare
jahorton
commented
May 21, 2026
Comment on lines
+615
to
+619
| export interface ContextTokenLike { | ||
| exampleInput: string; | ||
| isPartial?: boolean; | ||
| sourceRangeKey?: string; | ||
| } |
Contributor
Author
There was a problem hiding this comment.
Resolve: this is separate (at present) from one added earlier in #15992.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
To better handle inputs that shift the word-boundary in some custom models and models released before Keyman 14.0, this PR provides generalized re-use of the whitespace-based token-transition algorithm used for our most prominently-supported models.
Build-bot: skip build:web
Test-bot: skip