The use of "-" in snippet prefixes should be prohibited.

[kakogawa]

Prerequisites

• I have written a descriptive issue title.
• I have searched all issues to ensure it has not already been reported.

Summary

In the settings of Visual Studio Code, by setting editor.snippetSuggestions to "top",
snippets are displayed at the top of the suggestions, making it easier to write code.
However, unnecessary snippets may be prioritized and displayed, which can reduce productivity.

For example

Get-ChildItem -

When I type this, the expected candidates should be these options.

However, actually, unnecessary snippets are prioritized for display.

The reason for this is that when "-" is typed, snippets containing "-" in the prefix are prioritized for display.
I think this is a specification that reduces productivity.

Proposed Design

I think that the use of "-" in snippet prefixes should be prohibited.

For example
"prefix": "do_until"
"prefix": "doUntil"

Many prefixes use "-" in snippets\PowerShell.json,
but I don't think it's absolutely necessary to use "-".
I was able to address this issue by replacing all "-" in the prefix of "PowerShell.json" to "_".

Please consider this. Thank you.

[JustinGrote]

Thanks for the suggestion! Have you tried setting editor.snippetSuggestions to bottom? That'll get you the behavior you are looking for without us having to take a breaking change on all the snippets. You will also want to make sure that your PowerShell Extension terminal is running and unblocked otherwise it cannot generate parameter intellisense.

[github-actions]

This issue has been labeled as resolved, please verify the provided fix (or other reason).

[kakogawa]

I already tried setting editor.snippetSuggestions to bottom once.
However, when set to bottom, the snippets are displayed at the very bottom, which becomes inconvenient.
I am looking for snippets in most situations. Therefore, I have it set to top.
However, when I want to input command options, snippets are unnecessary.
That's because what I'm looking for at that time are options.
I believe that the most appropriate suggestion should be displayed according to the situation.

[JustinGrote]

For customizing snippet suggestions on context, that would have to be a vscode feature update to allow it to be customizable per symbol type, and not something we can do here.

The insert snippet command (default keybinding ctrl-alt-J) is there if you explicitly want to select and search a snippet list.

You can also use the Control Snippets (https://marketplace.visualstudio.com/items?itemName=svipas.control-snippets) extension to disable the powershell snippets and replace them with your own versions that don't have the dash, the snippets are transferrable from the snippets file: https://github.com/PowerShell/vscode-powershell/blob/main/snippets/PowerShell.json and then fix the snippet names yourself.

I know this isn't the answer you want to hear but introducing a breaking change to the snippets may have someone else coming here that they are annoyed they now have to type underscores which is an extra shift-key and slows them down and whatnot, so unless there is a really strong justification and support to change, it's probably not going to happen (sorry), but there are ways to get the environment you want.

[github-actions]

This issue has been labeled as resolved, please verify the provided fix (or other reason).

[kakogawa]

introducing a breaking change to the snippets may have someone else coming here that they are annoyed they now have to type underscores which is an extra shift-key and slows them down and whatnot, so unless there is a really strong justification and support to change.

It is not always necessary to use “_”.
“prefix”: “doUntil”
CamelCase like this is also acceptable.
At least, I don’t think it’s appropriate to include a “-” that has no necessity, as it would conflict with the option's “-”.