change(web): remove TokenizationCorrector class only used in epic/boundary-correction - #16581
Merged
Merged
Conversation
…ndary-correction Build-bot: skip build:web Test-bot: skip
User Test ResultsTest specification and instructions User tests are not required Test Artifacts
|
github-actions
Bot
added
web/
web/predictive-text/
change
Member
|
How did keymanweb.js end up 1641 bytes larger than before? Or is the check confused? |
Contributor
Author
I'm going to guess it's #16450, which was probably merged since the last alpha build. |
mcdurdin
approved these changes
Sep 18, 2026
Collaborator
|
Changes in this pull request will be available for download in Keyman version 19.0.288-alpha |
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
3 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.
This class, intended for use in epic/boundary-correction, had an early version 'land' in epic/autocorrect. It's only used in unit tests, though, and is not integrated into the predictive-text engine. Furthermore, some changes we may want for this release cycle will require we either remove this set of classes or patch them up... so let's just drop them for 19.0 beta and restore them on epic/boundary-correction.
Build-bot: skip build:web
Test-bot: skip