Merge pull request #33 from chaploud/master

Change `cpt.showCommands` command's prefix `>CPT` to `>[CPT]` for more accurate filtering

* Fixes #32

Author: PEZ

CHANGELOG.md

@@ -4,6 +4,8 @@ Changes to Calva Power Tools
 
 ## [Unreleased]
 
+- [Change cpt.showCommands prefix](https://github.com/BetterThanTomorrow/calva-power-tools/issues/32)
+
 ## [v0.0.9] - 2025-05-16
 
 - [Add Dataspex tool](https://github.com/BetterThanTomorrow/calva-power-tools/issues/29)

CONTRIBUTING.md

@@ -16,7 +16,7 @@ The default way of progress for a change to this project is:
 
 We prefer that each pull request is focused on one problem at the time. Even if sometimes related Issues can be addressed by the same changes.
 
-As part of your PR you update the `**[Unrelased]**` section of CHANGELOG.md, linking to the issue(s) addressed. WHen a new version of the extension is released a changelog entry will be created with everything that is in the unreleased section. The Changelog should read like a story of how the extension has evolved since its creation.
+As part of your PR you update the `**[Unreleased]**` section of CHANGELOG.md, linking to the issue(s) addressed. WHen a new version of the extension is released a changelog entry will be created with everything that is in the unreleased section. The Changelog should read like a story of how the extension has evolved since its creation.
 
 When you file a pull request some CI jobs will run:
 

src/calva_power_tools/extension.cljs

@@ -14,9 +14,9 @@
 
 (defn show-commands!
   ([]
-   (vscode/commands.executeCommand "workbench.action.quickOpen" ">CPT "))
+   (vscode/commands.executeCommand "workbench.action.quickOpen" ">[CPT] "))
   ([s]
-   (vscode/commands.executeCommand "workbench.action.quickOpen" (str ">CPT " s " "))))
+   (vscode/commands.executeCommand "workbench.action.quickOpen" (str ">[CPT] " s " "))))
 
 (defn ^:export activate [context]
   (js/console.time "activation")