spiegel-keyman/web/src/engine/predictive-text
Joshua Horton 012dcaeee9 refactor(web): differentiate between true and represented inputs for context tokens
To be up-front, this is looking ahead significantly to epic/dict-breaker (#12142) concerns.  The core idea here:  each token should mark which part of the current context it represents - and the best data for the job happens to be the original, true transforms.

With epic/dict-breaker and other possible work that would faciltate considering alternative tokenizations, it is quite possible the original source transform(s) for a tokenization may not actually be represented within that tokenization's input set.

Consider:  if the spacebar appears as a fat-finger alternate for a letter key, we may wish to model an alternate tokenization where we actually _used_ that keystroke as a whitespace instead of a standard letter.  The resulting whitespace token shouldn't have the original letter key's transform as part of its represented inputs for such a case.

Build-bot: skip build:web
Test-bot: skip
2025-09-19 09:27:17 -05:00
..
templates Merge branch 'epic/autocorrect' into chore/merge-master-into-autocorrect 2025-09-03 12:37:49 -05:00
types change(web): replace USVString with string in predictive-text engine 2025-04-29 10:47:20 +07:00
wordbreakers Merge branch 'epic/autocorrect' into chore/merge-master-into-autocorrect 2025-08-28 01:33:18 -07:00
worker-main Merge branch 'feat/web/punctuation-whitespace-reversion' into feat/web/auto-accept-on-punctuation 2025-09-03 12:21:33 -05:00
worker-thread refactor(web): differentiate between true and represented inputs for context tokens 2025-09-19 09:27:17 -05:00
build.sh maint(common): consolidate builder scripts 2025-08-02 08:11:24 +10:00