fix(amazonq): handle explain, refactor, fix, optimize, sendToPrompt #7169
Conversation
|
| await focusAmazonQPanel.execute(placeholder, 'keybinding') | ||
| }) | ||
|
|
||
| const getCommandTriggerType = (data: any): EditorContextCommandTriggerType => { |
There was a problem hiding this comment.
I am assuming this fixes the double registering that was happening before?
There was a problem hiding this comment.
yeah I think what was happening was we were creating the commands here + the commands from commands.ts
| }) | ||
| export function registerCommands() { | ||
| /** | ||
| * make these no-ops, since theres still callers that need to be deprecated |
There was a problem hiding this comment.
are these commands still exposed to the user? Should we disable them until they are hooked up?
There was a problem hiding this comment.
They're only still enabled because other parts of the extension (like security scan) call them. In a future PR i'm going to fully deprecate them here and implement them in commands.ts but for now this just avoids spamming the logs with command not found
| return data === undefined ? 'keybinding' : 'contextMenu' | ||
| } | ||
|
|
||
| export function registerCommands(controllerPublishers: ChatControllerMessagePublishers) { |
There was a problem hiding this comment.
Just to verify, these still register properly on non-hybrid chat right?
There was a problem hiding this comment.
yeah this is only broken for hybrid chat, everything works fine for the regular main branch
2 participants
Problem
explain, refactor, fix, optimize right click menus aren't working
Solution
re-enable them through flare's genericCommand message
TODO
both of these need flare API changes to send generic prompts from the frontend to the backend
feature/xbranches will not be squash-merged at release time.