Slash commands can tell you which effort level they defaulted to when you didn't specify one.
What's wrong with this entry?
Command dispatch gained two optional hooks, onUserTypedArgs for interactive invocations and getDefaultEffort, whose returned .notice is rendered as a notice message when the user did not type an effort explicitly.
- effort resolution order for a command is now
getEffort ?? getDefaultEffort()?.value ?? effort onUserTypedArgsfires only for interactive invocations, not programmatic dispatch- the notice is shown only when no explicit effort was typed, so a user-supplied effort stays silent
let k = g.getDefaultEffort?.(A, n)?.notice;
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
A crashing slash command now tells you it crashed
Both mention slash command
-
v2.1.234
A command can decide from its arguments whether it counts as sensitive
Both mention slash command
-
v2.1.234
A slash-command grouping for a command that does not exist
Both mention slash command