Use it now
Useful2 Signal2
Custom commands can mark subcommands bare-only, so extra words go to the parent command.
What's wrong with this entry?
Anonymous. No account, no email.
subcommandsBareOnly
What
Command definitions gained a subcommandsBareOnly field. When it is set, a subcommand name only matches if nothing follows it, so typing /foo bar baz runs the parent /foo command with bar baz as its arguments instead of dispatching to the bar subcommand.
Details
- Carried through both prompt-backed and file-backed command construction, and added to the allow-list used when commands are serialized.
- Dispatch bails out on trailing text:
if (e.subcommandsBareOnly && s !== "") return;. - The field did not exist in v2.1.226.
Evidence
if (e.subcommandsBareOnly && s !== "") return;, subcommandsBareOnly
Strings lifted out of the shipped bundle, so the claim above can be checked against them.