@tusile/bot 0.1.0 → 0.1.2

package/README.md

@@ -90,10 +90,14 @@ await i.acknowledge();              // a press that needs no visible change
 A private answer is not channel history: nobody else ever sees it, it is not searchable or
 exportable, and it is gone within a day.
 
-If a handler takes longer than eight seconds, the SDK defers on its behalf rather than let
-the window run out. If a handler throws, or returns without answering, the person is told
-something went wrong instead of being left watching a spinner, and the error reaches
-`bot.on('error')`.
+If a command or form handler takes longer than eight seconds, the SDK defers on its behalf
+rather than let the window run out. A button handler is left alone: a press is answered by
+rewriting the message it sits on, and that is only available before the interaction has
+been answered at all, so deferring for you would trade a late answer for one that cannot be
+given. A slow press should defer and `followUp`.
+
+If a handler throws, or returns without answering, the person is told something went wrong
+instead of being left watching a spinner, and the error reaches `bot.on('error')`.
 
 ## Embeds and controls
 
@@ -115,7 +119,7 @@ await i.reply({
     components: [
       { type: 'button', style: 'primary', label: 'Press me', custom_id: 'vote:yes' },
       { type: 'button', style: 'danger', label: 'No', custom_id: 'vote:no' },
-      { type: 'button', style: 'link', label: 'Docs', url: 'https://tusile.com/bots.html' },
+      { type: 'button', style: 'link', label: 'Docs', url: 'https://tusile.com/bots' },
     ],
   }],
 });
@@ -129,8 +133,9 @@ whatever state you need in it: `page:3`, `vote:close:99`. An exactly registered
 a prefix, and the longest matching prefix wins, so a general handler cannot swallow presses
 meant for a specific one.
 
-Button styles are `primary`, `secondary`, `success`, `danger` and `link` (which takes a
-`url` instead of a `custom_id`). A row can hold five buttons, or one select.
+Button styles are `primary`, `secondary`, `danger` and `link` (which takes a `url` instead
+of a `custom_id`). Anything else draws as a plain button rather than not at all. A row can
+hold five buttons, or one select.
 
 ## Forms
 
@@ -229,6 +234,6 @@ commands, a custom status line, gateway resume after a drop (it reconnects and r
 instead), and outbound webhooks.
 
 Full reference, including every field of an embed, a component and a command option:
-**https://tusile.com/bots.html**
+**https://tusile.com/bots**
 
 MIT licensed.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tusile/bot",
-  "version": "0.1.0",
+  "version": "0.1.2",
   "description": "Write a Tusile bot: slash commands, buttons, forms and voice, over an outbound WebSocket.",
   "type": "module",
   "main": "src/index.js",
@@ -27,7 +27,7 @@
     "chat",
     "slash-commands"
   ],
-  "homepage": "https://tusile.com/bots.html",
+  "homepage": "https://tusile.com/bots",
   "license": "MIT",
   "author": "Tusile"
 }

package/src/dispatch.js

@@ -120,9 +120,14 @@ export class Dispatcher {
    *
    * Cancelled the moment the handler returns, and it checks again before sending: an
    * unasked-for defer arriving after a normal answer would be refused every time.
+   *
+   * Not for a press. A press is answered by rewriting the message it sits on, and that is
+   * only available before the interaction has been answered at all; after a bare defer the
+   * server has no message to edit and refuses. Deferring on the handler's behalf would
+   * trade a late answer for one that cannot be given, and leave the buttons live.
    */
   #deferAfterAWhile(interaction) {
-    if (!(this.#autoDeferMs > 0)) return { cancel() {} };
+    if (!(this.#autoDeferMs > 0) || interaction.isComponent) return { cancel() {} };
     const timer = setTimeout(() => {
       if (interaction.answered) return;
       interaction.defer().catch((err) => this.#onError(err, interaction));