Every message has a row under it to reply or react. Replying quotes the message above the composer, and the sent message stores reply_to_message_id (a plain id, not a foreign key, so deleting the quoted message only drops the quote). send-message accepts a quote from any session of the same conversation, so a rollover or a thread that moved on still sends; the conversation drops a picked quote when its session changes. The bot reads the quote as "[Replying to ...]" before the user's turn, file-only replies included, and relayed messages carry it too. Reactions are a fixed set (BotMessageReactions) in bot_message_reactions, one per message, emoji and user or bot. Users toggle their own through api/admin/bots/react-message, and every bot gets react_to_message for the session it answers (the user's latest message by default). Both push the fresh list as server:bot-reaction, with mine worked out for the session's user. Co-Authored-By: Claude Opus 5.5 <[email protected]>
33 lines
916 B
TypeScript
33 lines
916 B
TypeScript
import BunSQLite from "@moduletrace/bun-sqlite";
|
|
import type { BUN_SQLITE_COBBLE_BOT_MESSAGES } from "@/db/types/db";
|
|
import AppError from "@/src/utils/app-error";
|
|
|
|
type Params = {
|
|
user_id: number | string;
|
|
message_id: number | string;
|
|
};
|
|
|
|
/**
|
|
* A message in one of the user's own sessions, whoever wrote it. Throws
|
|
* when it isn't theirs.
|
|
*/
|
|
export default async function grabUserBotMessage({
|
|
user_id,
|
|
message_id,
|
|
}: Params): Promise<BUN_SQLITE_COBBLE_BOT_MESSAGES> {
|
|
const message = (
|
|
await BunSQLite.sql<BUN_SQLITE_COBBLE_BOT_MESSAGES>({
|
|
sql: `SELECT m.* FROM bot_messages m
|
|
JOIN bot_sessions s ON s.id = m.session_id
|
|
WHERE m.id = ? AND s.user_id = ? LIMIT 1`,
|
|
values: [message_id, user_id],
|
|
})
|
|
).payload?.[0];
|
|
|
|
if (!message?.id) {
|
|
throw new AppError(`Message not found`);
|
|
}
|
|
|
|
return message;
|
|
}
|