Commands can now decide from their arguments whether to be treated as sensitive; nothing shipped uses it yet.
Argument-dependent command sensitivity is wired through the transcript and input handler, but no shipped command uses the function form.
What's wrong with this entry?
A slash command's sensitivity can now be a function of the text typed after it, not just a fixed yes or no, and the same check is used by both the transcript and the input handler. The "isn't available over Remote Control" rejection now echoes the command as /name *** when it is sensitive instead of repeating what you typed. No command shipped in this build uses the function form.
isn't available over Remote Control.
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.235
Slash-command arguments are redacted before they appear in the transcript
Both mention slash command
-
v2.1.236
Pressing Enter on a typed slash command runs it
Both mention slash command
-
v2.1.238
Ctrl-C no longer wipes a slash-command rename
Both mention slash command