You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Restore the pre-refactor validation that combining --project and --global
on `list` is an error, not a silent equivalent of --scope=both. Moved the
check into parseScopeFlag itself so it applies uniformly across commands.
- For commands that pass allowBoth=false (install, uninstall), the
invalid-value error no longer mentions "both" as a valid option.
- Added TestUpdateScopeFlag and TestUninstallScopeFlag covering the new
Cobra wiring (--scope=global/both, invalid value, legacy-flag conflict,
and both-deprecated-flags-together cases). Introduced updateSkillsFn and
uninstallSkillsFn package-level test-injection vars mirroring the
existing installSkillsForAgentsFn pattern in install.go.
Co-authored-by: Isaac
{name: "scope conflicts with legacy project", args: []string{"--scope", "global", "--project"}, wantErr: "cannot use --scope with --project or --global"},
40
+
{name: "legacy both flags together rejected", args: []string{"--project", "--global"}, wantErr: "cannot use --global and --project together"},
{name: "scope conflicts with legacy project", args: []string{"--scope", "global", "--project"}, wantErr: "cannot use --scope with --project or --global"},
41
+
{name: "legacy both flags together rejected", args: []string{"--project", "--global"}, wantErr: "cannot use --global and --project together"},
0 commit comments