mirror of
https://github.com/openclaw/openclaw.git
synced 2026-05-28 01:22:57 +00:00
bbbed264b6
* docs(channels/slack,telegram): document ackReactionScope and its DM-excluding default The Slack and Telegram channel docs documented `ackReaction` but not `ackReactionScope`, even though the scope (defaulting to `group-mentions`) silently excludes DMs. People who set `ackReaction` and expect to see an emoji on DMs are surprised when nothing fires. This adds: - The resolution order for `ackReactionScope` (per-account → channel → `messages.ackReactionScope` → default `group-mentions`). - The full list of scope values (`all`, `direct`, `group-all`, `group-mentions`, `off`/`none`). - A Note callout flagging that the default does not react in DMs and that `messages.ackReactionScope` requires a gateway restart to take effect. - A short JSON example for the common case (`ackReactionScope: "all"`). Mirrors the structure already used in `docs/channels/matrix.md`. Found while configuring Slack DMs to show `👀` ack reactions and discovering that the docs covered the emoji but not the scope gate. AI-assisted. * fixup: scope is messages-only for Slack & Telegram (not per-account) Reviewer correctly noted that the Slack and Telegram runtimes only read `cfg.messages?.ackReactionScope` and the per-account/per-channel `ackReactionScope` keys don't exist in those schemas (only Discord and Matrix support them). Drop the misleading resolution-order bullets and document `messages.ackReactionScope` only. Verified against: - extensions/slack/src/monitor/provider.ts:243 - extensions/telegram/src/bot-core.ts:262 - src/config/types.slack.ts (no ackReactionScope in account schema) - src/config/types.telegram.ts (no ackReactionScope in account schema) Keeps the DM-default gotcha, the full enum, and the gateway-restart note, which were the original value of the PR. --------- Co-authored-by: Dr. Claw <drclaw-iq@users.noreply.github.com>
