openclaw-vainplex/src/slack/monitor
Jonathan Wilkins 09ce6ff99e fix(slack): respect top-level requireMention config
The `channels.slack.requireMention` setting was defined in the schema
but never passed to `resolveSlackChannelConfig()`, which always
defaulted to `true`. This meant setting `requireMention: false` at the
top level had no effect—channels still required mentions.

Pass `slackCfg.requireMention` as `defaultRequireMention` to the
resolver and use it as the fallback instead of hardcoded `true`.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-01-15 02:17:27 +00:00
..
events feat(config): gate channel config writes 2026-01-15 01:41:15 +00:00
message-handler fix(slack): respect top-level requireMention config 2026-01-15 02:17:27 +00:00
allow-list.ts chore: migrate to oxlint and oxfmt 2026-01-14 15:02:19 +00:00
auth.ts chore: migrate to oxlint and oxfmt 2026-01-14 15:02:19 +00:00
channel-config.test.ts fix(slack): respect top-level requireMention config 2026-01-15 02:17:27 +00:00
channel-config.ts fix(slack): respect top-level requireMention config 2026-01-15 02:17:27 +00:00
commands.ts chore: migrate to oxlint and oxfmt 2026-01-14 15:02:19 +00:00
context.ts fix(slack): respect top-level requireMention config 2026-01-15 02:17:27 +00:00
events.ts refactor(src): split oversized modules 2026-01-14 01:17:56 +00:00
media.ts refactor(src): split oversized modules 2026-01-14 01:17:56 +00:00
message-handler.ts refactor(src): split oversized modules 2026-01-14 01:17:56 +00:00
policy.ts refactor(src): split oversized modules 2026-01-14 01:17:56 +00:00
provider.ts fix(slack): respect top-level requireMention config 2026-01-15 02:17:27 +00:00
replies.ts refactor: unify markdown formatting pipeline 2026-01-15 00:31:07 +00:00
slash.ts fix(slack): respect top-level requireMention config 2026-01-15 02:17:27 +00:00
types.ts feat(config): gate channel config writes 2026-01-15 01:41:15 +00:00