-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Async completion bug fixes #28219
Async completion bug fixes #28219
Conversation
/// This method needs to support custom procesing of commit characters to be on par with the old completion implementation. | ||
/// TODO we should consider removign this method and arrange better processing of commit characters. | ||
/// </summary> | ||
private bool IsCommitCharacter(char typeChar, ImmutableArray<CharacterSetModificationRule> rules) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
two space between private and bool. #Resolved
private bool IsCommitCharacter(char typeChar, ImmutableArray<CharacterSetModificationRule> rules) | ||
{ | ||
// Tab, Enter and Null (call invoke commit) are always a commit character | ||
if (typeChar == '\t' || typeChar == '\n' || typeChar == '\0') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it seriously worries me that:
- Enter is being sent through as typing '\n'.
- Commit is being sent through as typing \0
#Pending
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, Cyrus!
I just tried to be on par (comparing unit tests) with the old implementation. However, as I understand, previously we were able to handle e.g. Enter independently on all other key strokes. Now we have to make almost all decisions within the TryCommit method. So, we should process '\n' and '0' here. Do you have a suggestion?
In reply to: 200802172 [](ancestors = 200802172)
Merged into #29016 |
Fixes: #27692, #27693