What was wrong:snapshot, config, remote, database and completion had no Run. cobra checks a command's arguments only when it has one; otherwise it prints the help and reports success. So vaultik snapshot craete, vaultik config inti and vaultik completion nosuchshell printed help and exited 0, and a crontab line with such a typo made no backup and reported no error.
What changed: each group now accepts no arguments and prints its help when given none. Any other word fails as unknown command "craete" for "vaultik snapshot" with exit 1, as vaultik bogus does at the top level. A new test covers all five groups, with a mistyped word and with the group name alone.
cobra adds the completion command only inside Execute, so NewRootCommand now adds it itself and gives it a Run.
Things the diff does not show:
The completion scripts go to os.Stdout as it was when NewRootCommand ran, so a later SetOut does not redirect them. Entry is unaffected.
A group's help now has a usage line such as vaultik snapshot [flags] above vaultik snapshot [command]. The top-level help already has the same pair.
Judgement call: the error leaves out the "Did you mean" suggestion that the top level gives. Adding one would take a hand-written argument check.
Model: opus-5-5
Fixes https://git.eeqj.de/sneak/vaultik/issues/319.
**What was wrong:** `snapshot`, `config`, `remote`, `database` and `completion` had no Run. cobra checks a command's arguments only when it has one; otherwise it prints the help and reports success. So `vaultik snapshot craete`, `vaultik config inti` and `vaultik completion nosuchshell` printed help and exited 0, and a crontab line with such a typo made no backup and reported no error.
**What changed:** each group now accepts no arguments and prints its help when given none. Any other word fails as `unknown command "craete" for "vaultik snapshot"` with exit 1, as `vaultik bogus` does at the top level. A new test covers all five groups, with a mistyped word and with the group name alone.
cobra adds the completion command only inside Execute, so `NewRootCommand` now adds it itself and gives it a Run.
**Things the diff does not show:**
- The completion scripts go to `os.Stdout` as it was when `NewRootCommand` ran, so a later `SetOut` does not redirect them. `Entry` is unaffected.
- A group's help now has a usage line such as `vaultik snapshot [flags]` above `vaultik snapshot [command]`. The top-level help already has the same pair.
Judgement call: the error leaves out the "Did you mean" suggestion that the top level gives. Adding one would take a hand-written argument check.
Model: opus-5-5
clawbot
self-assigned this 2026-10-13 11:19:23 +02:00
snapshot, config, remote, database and completion had no Run, and
cobra checks a command's arguments only when it has one, so `vaultik
snapshot craete` printed the group's help and exited 0. Each group now
prints its help only when given no argument; any other word fails as
an unknown command with exit 1, as at the top level.
cobra adds the completion command only when Execute runs, so the root
command now adds it itself to give it a Run. Its scripts then go to
os.Stdout as it was at that moment; a later SetOut does not redirect
them.
Judgement call: the error has no "Did you mean" suggestion, which the
top level gives.
Model: opus-5-5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Fixes #319.
What was wrong:
snapshot,config,remote,databaseandcompletionhad no Run. cobra checks a command's arguments only when it has one; otherwise it prints the help and reports success. Sovaultik snapshot craete,vaultik config intiandvaultik completion nosuchshellprinted help and exited 0, and a crontab line with such a typo made no backup and reported no error.What changed: each group now accepts no arguments and prints its help when given none. Any other word fails as
unknown command "craete" for "vaultik snapshot"with exit 1, asvaultik bogusdoes at the top level. A new test covers all five groups, with a mistyped word and with the group name alone.cobra adds the completion command only inside Execute, so
NewRootCommandnow adds it itself and gives it a Run.Things the diff does not show:
os.Stdoutas it was whenNewRootCommandran, so a laterSetOutdoes not redirect them.Entryis unaffected.vaultik snapshot [flags]abovevaultik snapshot [command]. The top-level help already has the same pair.Judgement call: the error leaves out the "Did you mean" suggestion that the top level gives. Adding one would take a hand-written argument check.
Model: opus-5-5
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.