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

Autocomplete does not always intelligently suggest expected items #1401

Closed
mjbvz opened this issue Apr 18, 2017 · 2 comments
Closed

Autocomplete does not always intelligently suggest expected items #1401

mjbvz opened this issue Apr 18, 2017 · 2 comments

Comments

@mjbvz
Copy link

mjbvz commented Apr 18, 2017

From @matej-zajacik on April 18, 2017 8:35

  • VSCode Version: Code 1.10.1 (653f8733dd5a5c43d66d7168b4701f94d72b62e5, 2017-03-02T00:33:15.706Z)
  • OS Version: Windows_NT ia32 10.0.14393
  • Extensions:
Extension Author Version
toml be5invis 0.0.2
dart-code DanTup 1.0.2
csharp ms-vscode 1.3.0

Autocomplete does not show up when an enumerator is expected as a function parameter, or when you type the "new" keyword after declaring a class member.

Steps to repro:

  1. Just write the following code and observe what happens when you reach the "..." mark.

     public class SomeClass
     {
     	private Dictionary<int, int> myDict = new ... // <- In Visual Studio, the autocomplete suggests "Dictionary<int, int>()". In Code, nothing shows up; you have to type it again.
    
     	public enum SomeType
     	{
     		Type1,
     		Type2
     	}
    
     	public void SetType(SomeType type)
     	{
     	}
    
     	public void Start()
     	{
     		SetType(... // <- In Visual Studio, the autocomplete options show up with the SomeType enum. In Code, nothing shows up.
     	}
     }
    

Expected:

  • Similar behavior as in Visual Studio 2015/2017. These issues are among the few Code lacks from VS.

Copied from original issue: microsoft/vscode#24939

@mjbvz
Copy link
Author

mjbvz commented Apr 18, 2017

From the description of the bug, I believe this is related to the completion providers that the C# extension registers. Please let me know if you believe the issue is with VSCode itself

@DustinCampbell
Copy link
Member

This is a duplicate of #146.

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

No branches or pull requests

2 participants