Conversation
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
… tests to use new spur type
…-legacy splits, merges
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
Build-bot: skip build:web Test-bot: skip
…o corrections could be found Build-bot: skip build:web Test-bot: skip
…eat/web/insertion-spurs
…nd-fix-pred-text-helpers
…est-quotient-specialized-splits
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>
Relates-to: #12893 Test-bot: skip
…y-correction chore: establish epic/boundary-correction 🔪
…-predictable-unless-needed
…(to be restored in followup PR)" This reverts commit da12b14.
…o-boundarycorrect change(web): merge epic/autocorrect into epic/boundary-correct (near end of A19S34) 🔪
…i-token-correction-search
…i-token-correction-search
…earch feat(web): add prepareTokenizationSearch helper method 🔪
…ction-search change(web): convert primary correction-search loop for white-space correction 🔪
…nto-boundary-correction
…boundary-correction auto: A19S34 merge epic/autocorrect into boundary-correction
…nto-boundary-correction
…boundary-correction auto: A19S35 merge epic/autocorrect into boundary-correction 🔪
User Test ResultsTest specification and instructions User tests are not required Test Artifacts
|
…nto-boundary-correction
…boundary-correction auto: A19S36 merge master into boundary-correction 🔪
…to-boundary-correction
…oundary-correction auto: B19S1 merge master into boundary-correction 🔪
This branch has not been deployed
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.
Test-bot: skip
Build-bot: skip build:web