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

Odd behaviour with Dictionary #5

Open
jchannon opened this issue Nov 4, 2014 · 8 comments
Open

Odd behaviour with Dictionary #5

jchannon opened this issue Nov 4, 2014 · 8 comments
Labels

Comments

@jchannon
Copy link
Member

jchannon commented Nov 4, 2014

This is what I get when typing
screen shot 2014-11-04 at 22 26 21

When I then type D i get a different completion and when accepted I get the snippet stuff for TKey,TValue, @nosami said it might be a server bug

screen shot 2014-11-04 at 22 26 55

@mat-mcloughlin
Copy link
Member

This looks like it could be a problem with omnisharp as the request looks ok. @nosami any thoughts?

@nosami
Copy link

nosami commented Nov 5, 2014

Which property are you using on the left hand side?

@nosami
Copy link

nosami commented Nov 5, 2014

If you are using snippeted completions, I think that you should use MethodHeader on the left, and ReturnType on the right.

@mat-mcloughlin
Copy link
Member

I'm using DisplayText on the left and ReturnType on the right atm. I'll change it

@mat-mcloughlin
Copy link
Member

As a possible extension to this bug there seems to be some inconsistent behaviour with intellisense when using property initialiser. If you attempt to invoke the auto complete when the curly brackets are on the same line like

var foo = new Foo { };

It will bring back the properties. However if you have the brackets on different lines it doesn't bring anything back:

var foo = new Foo
{
};

@jchannon
Copy link
Member Author

In Sublime I don't get the original bug now but maybe cause I changed to
snippet based completions

@nosami
Copy link

nosami commented Nov 20, 2014

The first issue is fixed now on the server. Don't know about the 2nd one yet.

@DonKarlssonSan
Copy link
Contributor

Since this issue is still open I interpret it as you also track the unresolved new Foo { }; problem that Mat described 16 Nov. I've looked into that a bit. I would say that this problem too is on the omnisharp-server side. Attaching an animated gif that displays both Brackets and the omnisharp-server responses beneath.
omnisharp_brackets_completion

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

No branches or pull requests

4 participants