Skip to content
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

Closed
wants to merge 24 commits into from

Conversation

ivanbasov
Copy link
Contributor

Fixes: #27692, #27693

@ivanbasov ivanbasov requested a review from a team as a code owner June 29, 2018 18:58
@ivanbasov ivanbasov requested a review from dpoeschl June 29, 2018 18:58
@ivanbasov ivanbasov added this to the 16.0 milestone Jun 29, 2018
@ivanbasov ivanbasov requested a review from a team as a code owner July 6, 2018 23:34
/// 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)
Copy link
Member

@CyrusNajmabadi CyrusNajmabadi Jul 7, 2018

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')
Copy link
Member

@CyrusNajmabadi CyrusNajmabadi Jul 7, 2018

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:

  1. Enter is being sent through as typing '\n'.
  2. Commit is being sent through as typing \0
    #Pending

Copy link
Contributor Author

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)

@ivanbasov
Copy link
Contributor Author

Merged into #29016

@ivanbasov ivanbasov closed this Aug 10, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants