Skip to content

epic: boundary-correction 🔪 - #16025

Closed
mcdurdin wants to merge 123 commits into
epic/autocorrectfrom
epic/boundary-correction
Closed

epic: boundary-correction 🔪#16025
mcdurdin wants to merge 123 commits into
epic/autocorrectfrom
epic/boundary-correction

Conversation

@mcdurdin

Copy link
Copy Markdown
Member

Test-bot: skip

jahorton and others added 26 commits April 22, 2026 14:56
Per the search quotient graph documentation, we should no longer have one node type handle all edit operation types.  Our current ("legacy") implementation and unit tests are most tailored for the needs of 'substitution' edit types, so this PR starts there.

Build-bot: skip build:web
Test-bot: skip
…ion-edit search-graph edges

Build-bot: skip build:web
Test-bot: skip
…d spur types

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

I happened to discover that the predictive-text "helper" fixtures' unit tests were not actually being run.  This links them in (during /worker-thread builds) to ensure they get run too.

Build-bot: skip build:web
Test-bot: skip
…o corrections could be found

Build-bot: skip build:web
Test-bot: skip
Co-authored-by: Eberhard Beilharz <ermshiperete@users.noreply.github.com>
Co-authored-by: Eberhard Beilharz <ermshiperete@users.noreply.github.com>
Co-authored-by: Eberhard Beilharz <ermshiperete@users.noreply.github.com>
…y-correction

chore: establish epic/boundary-correction 🔪
@keymanapp-test-bot

keymanapp-test-bot Bot commented May 28, 2026

Copy link
Copy Markdown

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")

jahorton and others added 2 commits July 6, 2026 07:49
…boundary-correction

auto: A19S32 merge epic/autocorrect into boundary-correction
@keyman-server keyman-server modified the milestones: A19S33, A19S34 Jul 20, 2026
keyman-server and others added 6 commits July 20, 2026 07:26
…o-boundary-correction

auto: A19S33 merge master into boundary-correction 🔪
This method is designed to determine the appropriate range of tokens, within each context variant, should be eligible for correction when generating predictions and corrections.

Build-bot: skip build:web
Test-bot: skip
@keyman-server keyman-server modified the milestones: A19S34, A19S35 Aug 3, 2026
jahorton and others added 10 commits August 4, 2026 01:10
…o-boundarycorrect

change(web): merge epic/autocorrect into epic/boundary-correct (near end of A19S34) 🔪
…earch

feat(web): add prepareTokenizationSearch helper method 🔪
…ction-search

change(web): convert primary correction-search loop for white-space correction 🔪
…boundary-correction

auto: A19S34 merge epic/autocorrect into boundary-correction
@keyman-server keyman-server modified the milestones: A19S35, A19S36 Aug 17, 2026
…boundary-correction

auto: A19S35 merge epic/autocorrect into boundary-correction 🔪
@mcdurdin
mcdurdin deleted the branch epic/autocorrect August 19, 2026 14:30
@mcdurdin mcdurdin closed this Aug 19, 2026
@github-project-automation github-project-automation Bot moved this from Todo to Done in Keyman Aug 19, 2026
@mcdurdin

Copy link
Copy Markdown
Member Author

Replaced by #16426

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

3 participants