Ignore slash commands containing slashes
Typing (or, more likely, pasting) a file path such as /data/some/thing in a post causes an error "Command with a trigger of data/some/thing not found". This happens surprisingly often in my workplace.
While the error does of course make sense and there are other things the user can do, I think it would be more user-friendly to disallow forward slashes in the names of actual slash commands, and do not attempt to process a word as a slash command if it contains slashes.
0
votes
gubbins
shared this idea
The error message now also includes the option “Click here to send as a message”.