From ae933b6429df5ab512cae99ada817f09651cd9d6 Mon Sep 17 00:00:00 2001 From: Travis Ralston Date: Fri, 29 Aug 2025 13:42:41 -0600 Subject: [PATCH] Fix argument references --- proposals/4332-in-room-bot-commands.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/proposals/4332-in-room-bot-commands.md b/proposals/4332-in-room-bot-commands.md index c7ddf489d..eab303d3e 100644 --- a/proposals/4332-in-room-bot-commands.md +++ b/proposals/4332-in-room-bot-commands.md @@ -131,7 +131,7 @@ When the user sends the command, the client creates either an `m.room.message` e }, "timeoutSeconds": 42, // integers and booleans use appropriate value types (converted from (probably) strings) "applyToPolicy": true, // tip: clients can convert user input like "yes" to booleans - "userId": ["@alice:example.org", "@bob:example.org"] // variadic arguments have array value types + "userId...": ["@alice:example.org", "@bob:example.org"] // variadic arguments have array value types // Note: all other types are represented as simple string values } @@ -193,7 +193,7 @@ The following extensions/features are best considered by future MSCs: * Some predefined validation on arguments, like a range for integers or maximum/minimum length of strings. -* Support for optional arguments. For example: `[userId]`, if a user ID is not required. +* Support for optional arguments. For example: `[roomId]`, if a room ID is not required. ## Potential issues