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
![](https://secure.gravatar.com/avatar/f350c83a46f05914ec5dcce233e7d12c?size=40&default=https%3A%2F%2Fassets.uvcdn.com%2Fpkg%2Fadmin%2Ficons%2Fuser_70-6bcf9e08938533adb9bac95c3e487cb2a6d4a32f890ca6fdc82e3072e0ea0368.png)
The error message now also includes the option “Click here to send as a message”.