Code completion inserts unnecessary tabstops in LSP

[sooxt98]

Is there a way to disable auto comma before this this get fix?

[DanTup]

Can you try adding "editor.suggest.snippetsPreventQuickSuggestions": false, to your VS Code settings, and see if that stops this from happening?

I think it might be being caused by the extra tab-stop.

[sooxt98]

@DanTup that's quick reply, ya that's magic it fixed

[sooxt98]

microsoft/vscode#102580

[DanTup]

Yeah, this is a common complaint. It is on the Dart-Code Recommended Settings page (https://dartcode.org/docs/recommended-settings/).

That said - I want to check whether we can do away with the final tabstop here, as that might prevent it from occurring. In any case, I'd recommend leaving that setting off :-)

[DanTup]

After some testing, I've decided to leave this as-is. Pre-LSP we would not include the additional tabstop, which meant this would not occur. However, you'd need to use the cursor key to move to after the comma.

In LSP, we have an additional tabstop which allows you to press <tab> after typing the argument value to jump after the tab. It feels slightly easier to hit <tab> than the cursor key to move after this, so I think it's worth keeping, given that we recommend snippetsPreventQuickSuggestions: false anyway.

[DanTup]

I've changed my mind. This could affect a lot of people when moving to LSP as it never used to happen. The benefit of using tab is minor, but the annoyance for all users that haven't applied the recommended settings (likely most) is likely greater.