A slash command that crashes now tells you, instead of silently clearing the screen.
What's wrong with this entry?
When one of the interactive slash commands throws, the error is reported back into the conversation as command stderr instead of the UI just clearing. Telemetry now separates a command you aborted from one that threw.
cmd_local_jsx_aborted
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