-
-
Notifications
You must be signed in to change notification settings - Fork 642
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reply to !eval message instead of pinging #2382
Comments
Sounds good to me, I don't see why not. |
What would happen when the command is invoked in a non-whitelisted channel? I suppose it'd have to still send a new message that pings in bot-commands? Also would the reply be ephemeral? We presumably don't want that, since a lot of the time the eval command is used to showcase something, meaning other people need to see the outcome. And I believe @bj0key, the user who raised this, said they'd like to implement this fwiw @Robin5605 |
Yeah this seems good. Sometimes the eval takes a while and returns a few messages after the original |
Yeah, I wouldn't mind implementing this. I think it'd also be worth having |
I can take on this! |
Sorry for not noticing your message earlier @bj0key, I assigned it to someone else, hope you don't mind. |
It was discussed in #community-meta if the
!eval
command should reply to the original command instead of sending a separate message with a ping. Thoughts on this? I'd be willing to PR if accepted.The text was updated successfully, but these errors were encountered: