Skip to content

Conversation

@mousetraps
Copy link
Contributor

  • do not enable COMPLETEWORD when OnlyTabOrEnterToCommit option is
    enabled

fix #455

…s selected

- do not enable COMPLETEWORD when OnlyTabOrEnterToCommit option is
  enabled
@billti
Copy link
Member

billti commented Sep 16, 2015

So this just causes it to show the list even if only one member? (I noticed this, but didn't think it was a big deal). 👍 if that's the only behavior change.

@mousetraps
Copy link
Contributor Author

Yep, that's the only behavior change - it's a bigger deal when IntelliSense is being automatically displayed because typing "const" automatically completes it to "constructor" since "const" isn't in the list and there's only one item selected.

mousetraps added a commit that referenced this pull request Sep 16, 2015
fix #455 IntelliSense commits too aggressively when completion is selected
@mousetraps mousetraps merged commit 33ac229 into microsoft:master Sep 16, 2015
@mousetraps
Copy link
Contributor Author

Gah, sorry I conflated two examples. The const thing applied only to one of the unit tests where ctrl+space was used to grab the completions list since spaces don't actually cause use to commit. But the user-facing issue was when assigning to a variable that didn't exist in isense.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

InteliSense commits too aggressively when completion is selected

3 participants