remove command succeeds even when plugin is not rescoped to the project#73
remove command succeeds even when plugin is not rescoped to the project#73erdembircan merged 6 commits intomasterfrom
remove command succeeds even when plugin is not rescoped to the project#73Conversation
|
[agent] Addressed the review feedback: extracted a |
erdembircan
left a comment
There was a problem hiding this comment.
Work on failed CI operations.
- Derive PluginBinding type from ClaudeCodeToolbox.getGlobalPluginConfig return type instead of using Record<string, string> - Apply Prettier formatting to multi-property makeBinding calls
|
[agent] Fixed the two CI failures: Typecheck -- The Lint (Prettier) -- The single-line All 124 tests pass, typecheck and lint are clean. |
The "not rescoped" message was using the full projectPath instead of shortPath, causing the output formatting test (merged from master) to fail. Also adds the missing getGlobalPluginConfig mock to the remove output test so the removal path proceeds instead of hitting the not-rescoped guard.
|
[agent] Fixed the failing test by merging master into the branch and addressing the incompatibility. Root cause: The PR branch was created before the
Changes:
All 127 tests pass, typecheck and lint are clean. |
|
[agent] Merged via squash into master. CI was green on the latest commit (07e544d) and the owner approved with LGTM. |
[agent]
Closes #71
unscopePluginnow checks whether the plugin has a binding for the current project before attempting removal. If no matching binding exists, it reports that and does nothing instead of unconditionally removing and logging success.