Skip to content

Conversation

@jahorton
Copy link
Contributor

With the various ways that tokenizations can transition depending upon which potential inputs are applied, it's possible for multiple different tokenizations to transition into the same one. As such, there will no longer be "just one" way that a tokenization is reached.

Accordingly, it's best to perform word-boundary realignment operations (splits, merges) separately from text-editing operations (inserts, deletes).

Build-bot: skip build:web
Test-bot: skip

@keymanapp-test-bot
Copy link

keymanapp-test-bot bot commented Nov 19, 2025

User Test Results

Test specification and instructions

User tests are not required

Test Artifacts

  • Web
    • KeymanWeb Test Home - build : all tests passed (no artifacts on BuildLevel "build")

@keymanapp-test-bot keymanapp-test-bot bot changed the title refactor(web): split tokenization realignment from evaluateTransition refactor(web): split tokenization realignment from evaluateTransition 🚂 Nov 19, 2025
@keymanapp-test-bot keymanapp-test-bot bot added this to the A19S16 milestone Nov 19, 2025
@keyman-server keyman-server modified the milestones: A19S16, A19S17 Nov 22, 2025
@keyman-server keyman-server modified the milestones: A19S17, A19S18 Dec 6, 2025
@keyman-server keyman-server modified the milestones: A19S18, A19S19 Dec 21, 2025
@keyman-server keyman-server modified the milestones: A19S19, A19S20 Jan 3, 2026
@keyman-server keyman-server modified the milestones: A19S20, A19S21 Jan 16, 2026
@jahorton jahorton force-pushed the feat/web/search-space-node-propagation branch from b31bcad to c303355 Compare January 21, 2026 21:52
@jahorton jahorton force-pushed the feat/web/search-space-node-propagation branch 3 times, most recently from beafeb6 to 36df714 Compare January 30, 2026 21:06
@keyman-server keyman-server modified the milestones: A19S21, A19S22 Jan 31, 2026
@jahorton jahorton force-pushed the refactor/web/realign-tokenization branch from 49391d5 to 3473c6f Compare February 3, 2026 14:48
With the various ways that tokenizations can transition depending upon which potential inputs are applied, it's possible for multiple different tokenizations to transition into the same one.  As such, there will no longer be "just one" way that a tokenization is reached.

Accordingly, it's best to perform word-boundary realignment operations (splits, merges) separately from text-editing operations (inserts, deletes).

Build-bot: skip build:web
Test-bot: skip
@jahorton jahorton force-pushed the feat/web/search-space-node-propagation branch from 36df714 to c2e0427 Compare February 5, 2026 19:43
@jahorton jahorton force-pushed the refactor/web/realign-tokenization branch from 3473c6f to 4f257f5 Compare February 5, 2026 19:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Todo

Development

Successfully merging this pull request may close these issues.

2 participants