You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to have a feature for Command which allows you to set actAsTypingUntilResponseIsSent to true. If you have asynchronous responses to commands, it is handy to inform the user that the bot is processing the request by using message.channel.startTyping(). Once the response has been sent message.channel.stopTyping() has to be executed again.
Implementing that for all commands is a repetitive task and I think this could be a nice feature for this framework.
The text was updated successfully, but these errors were encountered:
The best I could really do on the framework end is start the typing process before the command action is executed and stop it after. Maybe also have command.respond() stop it if it's used. Other than that it'd be clunky and not really fit with a lot of potential command designs, which is why it's never been something I've wanted as a part of the framework.
I'll consider it, and I'll leave this open as a reminder. If I make a decision either way I'll close this. I also definitely won't go for such a verbose option name if I do lol.
It would be nice to have a feature for
Command
which allows you to setactAsTypingUntilResponseIsSent
to true. If you have asynchronous responses to commands, it is handy to inform the user that the bot is processing the request by usingmessage.channel.startTyping()
. Once the response has been sentmessage.channel.stopTyping()
has to be executed again.Implementing that for all commands is a repetitive task and I think this could be a nice feature for this framework.
The text was updated successfully, but these errors were encountered: