OmniSharp / omnisharp-brackets

does some brackets stuff
49 stars 20 forks source link

Odd behaviour with Dictionary #5

Open jchannon opened 9 years ago

jchannon commented 9 years ago

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 commented 9 years ago

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

nosami commented 9 years ago

Which property are you using on the left hand side?

nosami commented 9 years ago

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

mat-mcloughlin commented 9 years ago

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

mat-mcloughlin commented 9 years ago

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 commented 9 years ago

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

nosami commented 9 years ago

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

DonKarlssonSan commented 9 years ago

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