command aws.codeWhisperer.rejectCodeSuggestion not found about aws-toolkit-vscode HOT 5 OPEN

@Will-ShaoHua hello and thanks for the quick reply.

I can confirm that this issue persists only when two inline completion extensions are enabled at the same time. Disabling Copilot made the popup disappear. Ideally, when auto suggestions are paused, I expect the ignoring code suggestions keymap to be disabled as well.

The sign-out approach is not going to work for me because signing out from CW causes a sign-out from Amazon Q as well, and I often toggle between Copilot Chat and Amazon Q during my daily workflow. As a workaround, I found that disabling the keybinding works better for me by adding the following override to my keybindings.json:

  {
    "key": "escape",
    "command": "-aws.codeWhisperer.rejectCodeSuggestion",
    "when": "aws.codewhisperer.connected && inlineSuggestionVisible && !editorReadonly || isCloud9 && suggestWidgetVisible && !editorReadonly"
  }

from aws-toolkit-vscode.

hey @dgokcin thanks for reporting to us.
Yes I think you can just sign out from CW and you should be still good to use AWS Toolkit.

I think the issue results from different inline completion extension interference (Copilot and CodeWhisperer), could you help me verify this aspect by disable Copilot and see if the issue persists? Thanks!

from aws-toolkit-vscode.

Ideally, when auto suggestions are paused, I expect the ignoring code suggestions keymap to be disabled as well.

Understood, we keep the keep binding because users can still trigger CW manually with [option] + [c]. But yes, we will figure out a way to mitigate this issue, after all not all users are aware of having multi inline completion providers is the root cause.

As a workaround, I found that disabling the keybinding works better for me by adding the following override to my keybindings.json

yea that works too!

from aws-toolkit-vscode.

Ideally, when auto suggestions are paused, I expect the ignoring code suggestions keymap to be disabled as well.

Understood, we keep the keep binding because users can still trigger CW manually with [option] + [c]. But yes, we will figure out a way to mitigate this issue, after all not all users are aware of having multi inline completion providers is the root cause.

As a workaround, I found that disabling the keybinding works better for me by adding the following override to my keybindings.json

yea that works too!

Fair enough. Thanks for looking into this.

from aws-toolkit-vscode.

This is particularly annoying when using Vim since it breaks the Escape key which is interpreted by VSCode as rejecting code suggestions.

from aws-toolkit-vscode.