Files
multica/packages/core/issues/surface/membership.test.ts
Naiyuan Qing ade6b34e5f MUL-3903: Extract shared issue surfaces (#4774)
* MUL-3903 refactor project issue surface state

Co-authored-by: multica-agent <github@multica.ai>

* Refactor project issue surface ownership

Co-authored-by: multica-agent <github@multica.ai>

* Extract shared issue surface entrypoints

Co-authored-by: multica-agent <github@multica.ai>

* Fix issue surface create defaults and selection reset

Co-authored-by: multica-agent <github@multica.ai>

* test(editor): add missing AbortSignal to suggestion items() calls

The suggestion items() contract gained a required signal param; the
mention/slash test call sites were never updated, breaking pnpm typecheck
for @multica/views.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* feat(issues): server-side assignee_types filter on ListIssues

ListGroupedIssues has taken assignee_types since squads shipped, but
ListIssues never did — so the workspace Members/Agents tabs had to fetch
the unfiltered workspace list and post-filter loaded pages client-side,
which made column totals and load-more pagination reflect the unfiltered
counts.

Add the same parse + WHERE clause to ListIssues (count query shares the
WHERE, so totals agree), thread the param through the TS client, and
widen MyIssuesFilter so scoped list caches can carry it.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* refactor(issues): route issue cache writes through a membership-aware coordinator

useUpdateIssue, useBatchUpdateIssues, and the WS issue:updated handler
each maintained their own similar-but-diverging patch/invalidate rules.
Consolidate them into cache-coordinator.ts (applyIssueChange /
rollbackIssueChange / invalidateIssueDerivatives) so local writes and
remote echoes follow one rules table by construction.

The coordinator is membership-aware via surface/membership.ts
(true | false | unknown against each list cache's own filter contract):

- a change that moves an issue off a filtered surface removes the card
  surgically (bucket total decremented) — fixes assignee changes leaving
  stale cards on My Assigned with no local safety net (previously only
  the WS echo recovered it), and replaces the blanket invalidate-myAll
  net for project moves (MUL-3669) with per-key precision
- possible entry into a loaded list marks that key stale — never
  hard-insert; page/slot is server knowledge
- stale keys flush on settle for mutations (a mid-flight refetch would
  stomp the optimistic state) and immediately for WS
- batch updates now patch detail + inbox like single updates; the
  off-screen bucket-count recovery previously exclusive to the WS path
  now covers local mutations too

Preserved invariants: synchronous optimistic patches (dnd-kit), MUL-3375
control-field stripping, and no refetch of surgically reconciled lists
(the drag-flicker fix).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* refactor(issues): resolve surfaces via core query plan/repository with window-keyed remount

Read-path convergence and the loading/empty semantics that fall out of
it:

- scope -> API params moves from scope.ts helpers into
  surface/query-plan.ts; workspace members/agents become server-filtered
  scoped plans (assignee_types) and the client postFilter machinery is
  deleted — tab counts and load-more are now exact
- query selection moves behind surface/repository.ts; the views data
  hook no longer branches on workspace-vs-scoped plumbing
- IssueSurfaceContent remounts on data-window change (wsId + scope):
  keepPreviousData placeholders keep sort/filter changes flicker-free
  within one window but must never let project A's (or workspace A's)
  cards impersonate B's with no loading state — cold window shows the
  skeleton, warm window hits cache instantly
- isEmpty is only asserted from full-window data; the gantt
  scheduled-only projection can't prove the window is empty, so GanttView's
  own "no scheduled issues" empty state renders instead of the generic
  create-issue one
- per-card project lookups hoist into a surface-level projectMap (drops
  a per-card useQuery), create-defaults typing tightens to
  IssueCreateDefaults

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* perf(issues): count-only arithmetic for off-window status/membership changes

An issue beyond a list's loaded page window used to force a full
first-page refetch just to fix two column counts. When the change is
CERTAIN (base entity known, membership definitive) the coordinator now
does the arithmetic locally:

- stayed a member + status changed: move one unit of total between the
  two buckets (loaded arrays untouched; hasMore stays consistent)
- left the list (reassigned / re-projected): old status bucket total -1
- member-to-member reassignment: counts unaffected, not even a stale key

Entering a list and any uncertainty (no base, unknown membership) still
refetch — the right page/slot is server knowledge. Branches on membership
OUTCOMES, not on which field changed, so future dimensions (team) join
automatically. Biggest win is the WS path: agents flipping off-screen
statuses no longer trigger refetch storms.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* feat(issues): deferred view-refresh indicator during placeholder revalidation

Sort/date changes (and any grouped-board filter change) revalidate behind
the previous snapshot — correct, but on a slow network the click felt
dead: content stays put and isLoading never fires. Surface the state as
isRefreshing (isPlaceholderData of the active query) and render a shared
ViewRefreshIndicator in every issues header: a fixed-width slot (zero
layout shift) whose spinner fades in after 300ms, so sub-second responses
show nothing (NN/g) while slow ones get a working signal.

Bound to the revalidation STATE, not to any particular control — any
current or future server-side view change lights it automatically.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: multica-agent <github@multica.ai>
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-02 14:11:10 +08:00

194 lines
5.7 KiB
TypeScript

import { describe, expect, it } from "vitest";
import type { Issue } from "../../types";
import {
issueChangedDims,
issueMatchesListFilter,
listFilterDependsOn,
} from "./membership";
function makeIssue(overrides: Partial<Issue> = {}): Issue {
return {
id: "issue-1",
workspace_id: "ws-1",
number: 1,
identifier: "MUL-1",
title: "Issue 1",
description: null,
status: "todo",
priority: "none",
assignee_type: "member",
assignee_id: "me",
creator_type: "member",
creator_id: "me",
parent_issue_id: null,
project_id: "p1",
position: 1,
stage: null,
start_date: null,
due_date: null,
labels: [],
metadata: {},
created_at: "2025-01-01T00:00:00Z",
updated_at: "2025-01-01T00:00:00Z",
...overrides,
};
}
describe("issueMatchesListFilter", () => {
it("judges assignee_id filters definitively", () => {
const issue = makeIssue();
expect(issueMatchesListFilter(issue, "assigned", { assignee_id: "me" })).toBe(true);
expect(issueMatchesListFilter(issue, "assigned", { assignee_id: "bob" })).toBe(false);
});
it("degrades to unknown when the entity is missing the filtered field", () => {
expect(
issueMatchesListFilter({ title: "partial" }, "assigned", { assignee_id: "me" }),
).toBe("unknown");
});
it("judges assignee_types filters, treating unassigned as a definitive miss", () => {
expect(
issueMatchesListFilter(makeIssue(), "workspace:members", {
assignee_types: ["member"],
}),
).toBe(true);
expect(
issueMatchesListFilter(makeIssue({ assignee_type: "agent" }), "workspace:members", {
assignee_types: ["member"],
}),
).toBe(false);
expect(
issueMatchesListFilter(
makeIssue({ assignee_type: null, assignee_id: null }),
"workspace:agents",
{ assignee_types: ["agent", "squad"] },
),
).toBe(false);
});
it("judges project filters", () => {
expect(
issueMatchesListFilter(makeIssue(), "project:p1", { project_id: "p1" }),
).toBe(true);
expect(
issueMatchesListFilter(makeIssue({ project_id: "p2" }), "project:p1", {
project_id: "p1",
}),
).toBe(false);
expect(
issueMatchesListFilter(makeIssue({ project_id: null }), "project:p1", {
project_id: "p1",
}),
).toBe(false);
});
it("never decides involves_user_id — the ownership graph is server-side", () => {
expect(
issueMatchesListFilter(makeIssue(), "agents", { involves_user_id: "me" }),
).toBe("unknown");
});
it("never decides the my:all union scope", () => {
expect(issueMatchesListFilter(makeIssue(), "all", {})).toBe("unknown");
});
it("ANDs across fields — a definitive miss beats an unknown", () => {
expect(
issueMatchesListFilter(
makeIssue({ project_id: "p2" }),
"scoped",
{ project_id: "p1", involves_user_id: "me" },
),
).toBe(false);
});
});
describe("issueChangedDims", () => {
it("treats written membership fields as changed when no base is known", () => {
expect(issueChangedDims({ assignee_id: "bob", assignee_type: "member" })).toEqual({
assignee: true,
project: false,
status: false,
});
expect(issueChangedDims({ project_id: null })).toEqual({
assignee: false,
project: true,
status: false,
});
});
it("sharpens against a base entity — writing the same value changes nothing", () => {
const base = makeIssue();
expect(issueChangedDims({ assignee_id: "me", assignee_type: "member" }, base)).toEqual({
assignee: false,
project: false,
status: false,
});
expect(issueChangedDims({ status: "todo" }, base).status).toBe(false);
expect(issueChangedDims({ status: "done" }, base).status).toBe(true);
expect(issueChangedDims({ project_id: "p2" }, base).project).toBe(true);
});
it("ignores non-membership fields", () => {
expect(issueChangedDims({ title: "x", position: 9 })).toEqual({
assignee: false,
project: false,
status: false,
});
});
});
describe("listFilterDependsOn", () => {
const none = { assignee: false, project: false, status: false };
it("my:all reacts to assignee changes only", () => {
expect(listFilterDependsOn("all", {}, { ...none, assignee: true })).toBe(true);
expect(listFilterDependsOn("all", {}, { ...none, project: true })).toBe(false);
});
it("assignee-keyed filters react to assignee changes", () => {
expect(
listFilterDependsOn("assigned", { assignee_id: "me" }, { ...none, assignee: true }),
).toBe(true);
expect(
listFilterDependsOn(
"workspace:members",
{ assignee_types: ["member"] },
{ ...none, assignee: true },
),
).toBe(true);
expect(
listFilterDependsOn("agents", { involves_user_id: "me" }, { ...none, assignee: true }),
).toBe(true);
expect(
listFilterDependsOn("assigned", { assignee_id: "me" }, { ...none, project: true }),
).toBe(false);
});
it("project filters react to project changes", () => {
expect(
listFilterDependsOn("project:p1", { project_id: "p1" }, { ...none, project: true }),
).toBe(true);
expect(
listFilterDependsOn("project:p1", { project_id: "p1" }, { ...none, assignee: true }),
).toBe(false);
});
it("creator filters never react — creator is immutable", () => {
expect(
listFilterDependsOn(
"created",
{ creator_id: "me" },
{ assignee: true, project: true, status: true },
),
).toBe(false);
});
it("the unfiltered workspace list never reacts", () => {
expect(
listFilterDependsOn(undefined, {}, { assignee: true, project: true, status: true }),
).toBe(false);
});
});