Closed martyychang closed 6 years ago
As a bonus it may be cool to check whether the Levenshtein distance between the bad command and a known command is 1, in which case the known command can be suggested as what the user was trying to execute
I think it would make more sense to create the generic "help" functionality in #23 before tackling this issue, because for truly unknown or unrecognizable commands the user should be referred to /clock help as the default feedback
Right now, when a user types an unrecognized command, an ugly HTTP 500 error is displayed as shown below.
Instead, it would be better for a more user-friendly message to be displayed, so the user knows what he or she did wrong. Below is a sample message from Slack displayed when an invalid command is entered.