In 0eefd80 I switched errors from the eval slash and message comments to be returned to the user as ephemeral messages. However, this doesn't seem to actually do anything.
-
For slash and message commands, we use defer() and then submit a followup. According to the docs, when using defer/DEFERRED_CHANNEL_MESSAGE_WITH_SOURCE, this is equivalent to editing the interstitial "defer" message, and so there's no way to make it ephemeral. We should probably remove this.
-
For the "Rerun" button, we use DEFERRED_UPDATE_MESSAGE and then submit a followup. We want to use this rather than using .defer(), as that shows a temporary "Loading" message to the user. However, for some reason which isn't documented, responding with an ephemeral doesn't do anything.
I don't know how much this matters in practice — hopefully errors aren't too common — but definitely annoying.
In 0eefd80 I switched errors from the eval slash and message comments to be returned to the user as ephemeral messages. However, this doesn't seem to actually do anything.
For slash and message commands, we use
defer()and then submit a followup. According to the docs, when usingdefer/DEFERRED_CHANNEL_MESSAGE_WITH_SOURCE, this is equivalent to editing the interstitial "defer" message, and so there's no way to make it ephemeral. We should probably remove this.For the "Rerun" button, we use
DEFERRED_UPDATE_MESSAGEand then submit a followup. We want to use this rather than using.defer(), as that shows a temporary "Loading" message to the user. However, for some reason which isn't documented, responding with an ephemeral doesn't do anything.I don't know how much this matters in practice — hopefully errors aren't too common — but definitely annoying.