Skip to content

Conversation

@iowillhoit
Copy link
Collaborator

@iowillhoit iowillhoit commented Oct 3, 2025

What does this PR do?

Temp fix for a tool rename to work with the VSCode extensions. Proper "tool alias" logic for renames is planned and will be added soon.

Old name works
Screenshot 2025-10-03 at 4 50 18 PM

New name works
Screenshot 2025-10-03 at 4 49 49 PM

Old name works and still fails alongside other invalid tools
Screenshot 2025-10-03 at 4 50 54 PM

What issues does this PR fix or reference?

@W-19814925@

@iowillhoit iowillhoit changed the title Temp tool rename fix W-19814925: Temp tool rename fix Oct 3, 2025
@cristiand391
Copy link
Member

QA notes:

verified a tool is available by the Configure tools view in vscode copilot.

"--tools", "open_org,create_lwc_component,create_scratch_org"
warning printed for the lwc tool and see it enabled as create_lwc_component_from_prd

"--tools", "open_org,create_lwc_component,create_scratch_org","--toolsets", "lwc-experts"
the tool referenced 2 times (old name via --tools and new name from the lwc toolset), warning printed for the old lwc name and enabled as create_lwc_component_from_prd.
The toolset tries to re-register create_lwc_component_from_prd but server handles it by skipping that second register:

Screenshot 2025-10-03 at 19 07 33

"--tools", "create_lwc_component"
enabling only that tool, still enabled as "--tools", "create_lwc_component_from_prd

@iowillhoit iowillhoit merged commit 3bcaa5d into main Oct 3, 2025
16 of 18 checks passed
@iowillhoit iowillhoit deleted the ew/temp-rename branch October 3, 2025 23:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants