fix(discord): replyToMode first behaviour

This commit is contained in:
CHISEN Kaoru
2026-02-07 08:10:58 +00:00
committed by Shadow
parent 4b3c9c9c5a
commit e25ae55879
4 changed files with 46 additions and 9 deletions

View File

@@ -200,14 +200,35 @@ describe("createReplyReferencePlanner", () => {
expect(planner.use()).toBe("parent");
});
it("prefers existing thread id regardless of mode", () => {
it("respects replyToMode off even with existingId", () => {
const planner = createReplyReferencePlanner({
replyToMode: "off",
existingId: "thread-1",
startId: "parent",
});
expect(planner.use()).toBeUndefined();
expect(planner.hasReplied()).toBe(false);
});
it("uses existingId once when mode is first", () => {
const planner = createReplyReferencePlanner({
replyToMode: "first",
existingId: "thread-1",
startId: "parent",
});
expect(planner.use()).toBe("thread-1");
expect(planner.hasReplied()).toBe(true);
expect(planner.use()).toBeUndefined();
});
it("uses existingId on every call when mode is all", () => {
const planner = createReplyReferencePlanner({
replyToMode: "all",
existingId: "thread-1",
startId: "parent",
});
expect(planner.use()).toBe("thread-1");
expect(planner.use()).toBe("thread-1");
});
it("honors allowReference=false", () => {