7b40d1b261
Adds support for separate replyToMode settings for DMs vs channels:
- Add channels.slack.dm.replyToMode for DM-specific threading
- Keep channels.slack.replyToMode as default for channels
- Add resolveSlackReplyToMode helper to centralize logic
- Pass chatType through threading resolution chain
Usage:
```json5
{
channels: {
slack: {
replyToMode: "off", // channels
dm: {
replyToMode: "all" // DMs always thread
}
}
}
}
```
When dm.replyToMode is set, DMs use that mode; channels use the
top-level replyToMode. Backward compatible when not configured.
30 lines
1.1 KiB
TypeScript
30 lines
1.1 KiB
TypeScript
import type {
|
|
ChannelThreadingContext,
|
|
ChannelThreadingToolContext,
|
|
} from "../channels/plugins/types.js";
|
|
import type { ClawdbotConfig } from "../config/config.js";
|
|
import { resolveSlackAccount, resolveSlackReplyToMode } from "./accounts.js";
|
|
|
|
export function buildSlackThreadingToolContext(params: {
|
|
cfg: ClawdbotConfig;
|
|
accountId?: string | null;
|
|
context: ChannelThreadingContext;
|
|
hasRepliedRef?: { value: boolean };
|
|
}): ChannelThreadingToolContext {
|
|
const account = resolveSlackAccount({
|
|
cfg: params.cfg,
|
|
accountId: params.accountId,
|
|
});
|
|
const configuredReplyToMode = resolveSlackReplyToMode(account, params.context.ChatType);
|
|
const effectiveReplyToMode = params.context.ThreadLabel ? "all" : configuredReplyToMode;
|
|
const threadId = params.context.MessageThreadId ?? params.context.ReplyToId;
|
|
return {
|
|
currentChannelId: params.context.To?.startsWith("channel:")
|
|
? params.context.To.slice("channel:".length)
|
|
: undefined,
|
|
currentThreadTs: threadId != null ? String(threadId) : undefined,
|
|
replyToMode: effectiveReplyToMode,
|
|
hasRepliedRef: params.hasRepliedRef,
|
|
};
|
|
}
|