fix: delete trailing ASCII when accepting prediction#300
Merged
Conversation
Member
Author
|
GA failure looked consistent with the I updated it to Verification on this branch:
This is included in commit |
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
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.
Summary
Context
With "Enable predictive typing in development" enabled, accepting a candidate after input like
おはようございmproducedおはようございmますbecause the trailing ASCII letter was ignored for matching but no longer deleted on accept after the recentdeleteCountrefactor.Testing
swift testcurrently fails before reaching these tests due to an upstream dependency build error inAzooKeyKanaKanjiConverter(DictionaryBuilder.swiftmissingimport OrderedCollectionsunder Swift 6.2 member import visibility checks)