I think the current behavior is a bit confusing and totally not something I would expect.

Let's run some scenarios:

Scenario 1

"editor.snippetSuggestions": "top",
"editor.suggestSelection": "first",

ctrl+space when writing ts

That's exactly what I expect

ctrl+space when trying to autocomplete some interface properties

That's NOT what I expect. If I'm trying to auto complete properties, they should be the first ones to be shown at all times.

Scenario 2

"editor.snippetSuggestions": "bottom",
"editor.suggestSelection": "first",

ctrl+space when writing ts

That's NOT what I expect. I'm trying to writing code, not instantiating a new thing. So snippets should take precedence over other stuff.

ctrl+space when trying to autocomplete some interface properties

That's exactly what I expect

=============================================

So, I hope I'm not asking too much here, but how can I mix both "modes" in a way that the editor is smart enough to "activate" the correct mode for the task?

I'm also having this issue too, when I ctrl + space I expect top result to be property of interfaces, classes .... not having to scroll up to find them.

When writing JavaScript, seeing a bunch of word selections signals to me that Intellisense lost track of my object and is considering it an any type. With the new behavior, it took me a few days to realize something was wrong with the suggestion box instead of the autocomplete. I think the old behavior should be the default.

There is two things that collide... For once our snippets aren't contextual and always computed (without any language smarts). So, they are always there but by default sitting at the bottom. With the new suggest-memories tho we might reveal them too aggressively. We can tweak that (e.g. don't use the memory when the line is empty).

Until then you can use this setting: "editor.suggestSelection": "first"

@jrieken I tried this, you can see in both my scenarios I had this set to "first", which still makes it unusable with either snippets or properties (depending on the editor.snippetSuggestions)

Yeah, once you "boost" snippets you will run in the issue of snippets being without context

@jrieken and if I don't boost the snippets, then snippets are not usable at all. Is there a way to rollback to the way it worked before? Or any set of configurations that emulates what we had before?

Setting this "editor.suggestSelection": "first" is actually the "before" behaviour.

idk man.. Me and everyone else here didn't have this issue before.. so I'm guessing something changed.

Well, I was out three weeks but I am pretty sure that I am the only one working this feature. The default value for editor.snippetSuggestions is inline (since at least 10 months). The implementation of top, bottom didn't change in more than a year.

The new feature is about selecting not sorting and to restore the old behaviour use: suggestSelection: first. That means always select the item sorted to the top.

I know that doesn't make this less frustrating and I totally agree with the static-snippet vs dynamic-completions dilemma but I don't think that this is new.

Makes sense. I'm not sure why I only noticed this now then. It was my first project with typescript, so maybe that's why 😝
Do you think what changed is the scroll position of the suggestions? Maybe that's why more people feel that the whole suggestion situation changed?

Did the vscode team broke something or it's a new feature? This behaviour never happened before.

Do you think what changed is the scroll position of the suggestions

Yeah, what's what I mean by selection. The first setting restores the old behaviour, the default should be conservative enough but there is plans to skip the memory when on an empty line

This comment explains what each setting does: #41060 (comment)

@jrieken

there is plans to skip the memory when on an empty line

I just got this:

I believe it's pre-selected override because of the prefix of a space (I typed @override on a blank line earlier), so I don't think the empty line rule will fix all the issues. Maybe the prefix should be ignored if there is any leading whitespace?