mirror of
https://seed.radicle.dev/rad:z4D5UCArafTzTQpDZNQRuqswh3ury.git
synced 2026-11-21 18:50:41 +08:00
The comment records only that it is resolved, so the name comes from the resolve operation in the patch's log. Adds the action to timeline threads too, and shapes the badge like a review's verdict.
38 lines
1.4 KiB
TypeScript
38 lines
1.4 KiB
TypeScript
import type { Author } from "@bindings/cob/Author";
|
|
import type { Operation } from "@bindings/cob/Operation";
|
|
import type { Action } from "@bindings/cob/patch/Action";
|
|
|
|
export interface Resolution {
|
|
author: Author;
|
|
timestamp: number;
|
|
}
|
|
|
|
/// Who last resolved each comment, taken from the patch's own operation log.
|
|
///
|
|
/// A `Comment` records only *that* it is resolved: `radicle`'s thread applies the
|
|
/// resolve op without keeping hold of its actor, so the comment itself cannot say
|
|
/// who. The op that did it is authored, though, so the log still can.
|
|
///
|
|
/// Unresolving drops the entry again, which is what leaves a comment that was
|
|
/// resolved and then reopened without one — matching `resolved: false` on the
|
|
/// comment. A revision's `resolves` set is deliberately not read: it records what
|
|
/// a revision claims to address and never marks a comment resolved.
|
|
export function resolutionsByComment(
|
|
activity: Operation<Action>[],
|
|
): Map<string, Resolution> {
|
|
const resolutions = new Map<string, Resolution>();
|
|
for (const op of [...activity].sort((a, b) => a.timestamp - b.timestamp)) {
|
|
for (const action of op.actions) {
|
|
if (action.type === "review.comment.resolve") {
|
|
resolutions.set(action.comment, {
|
|
author: op.author,
|
|
timestamp: op.timestamp,
|
|
});
|
|
} else if (action.type === "review.comment.unresolve") {
|
|
resolutions.delete(action.comment);
|
|
}
|
|
}
|
|
}
|
|
return resolutions;
|
|
}
|