Files
multica/packages/core/issues/surface/query-plan.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

170 lines
4.6 KiB
TypeScript

import type { CreateIssueRequest } from "../../types";
import type {
AssigneeGroupedIssuesFilter,
MyIssuesFilter,
} from "../queries";
import {
issueScopeKey,
UnsupportedIssueScopeError,
type IssueScope,
} from "./scope";
export type IssueSurfaceQueryPlan =
| {
kind: "workspace";
scopeKey: string;
queryScope: undefined;
queryFilter: MyIssuesFilter;
groupedScopeFilter: AssigneeGroupedIssuesFilter;
loadMoreScope: undefined;
loadMoreFilter: undefined;
userId: undefined;
createDefaults: Partial<CreateIssueRequest>;
}
| {
kind: "scoped";
scopeKey: string;
queryScope: string;
queryFilter: MyIssuesFilter;
groupedScopeFilter: AssigneeGroupedIssuesFilter;
loadMoreScope: string;
loadMoreFilter: MyIssuesFilter;
userId?: string;
createDefaults: Partial<CreateIssueRequest>;
};
function myRelationPlan(
scope: Extract<IssueScope, { type: "my" }>,
): Pick<
Extract<IssueSurfaceQueryPlan, { kind: "scoped" }>,
"queryScope" | "queryFilter" | "userId" | "createDefaults"
> {
switch (scope.relation) {
case "assigned":
return {
queryScope: "assigned",
queryFilter: { assignee_id: scope.userId },
userId: undefined,
createDefaults: {
assignee_type: "member",
assignee_id: scope.userId,
},
};
case "created":
return {
queryScope: "created",
queryFilter: { creator_id: scope.userId },
userId: undefined,
createDefaults: {},
};
case "involved":
return {
queryScope: "agents",
queryFilter: { involves_user_id: scope.userId },
userId: undefined,
createDefaults: {},
};
case "all":
return {
queryScope: "all",
queryFilter: {},
userId: scope.userId,
createDefaults: {},
};
}
}
export function buildIssueSurfaceQueryPlan(
scope: IssueScope,
): IssueSurfaceQueryPlan {
const scopeKey = issueScopeKey(scope);
switch (scope.type) {
case "workspace": {
// Members/Agents tabs are server-filtered scoped lists — assignee_types
// is a real API param on both the list and grouped endpoints, so each
// tab gets its own cache entry with correct per-status totals and
// load-more pagination. Only the unfiltered "all" tab uses the shared
// workspace list cache.
if (scope.actorKind === "members" || scope.actorKind === "agents") {
const queryFilter: MyIssuesFilter =
scope.actorKind === "members"
? { assignee_types: ["member"] }
: { assignee_types: ["agent", "squad"] };
return {
kind: "scoped",
scopeKey,
queryScope: scopeKey,
queryFilter,
groupedScopeFilter: queryFilter,
loadMoreScope: scopeKey,
loadMoreFilter: queryFilter,
userId: undefined,
createDefaults: {},
};
}
return {
kind: "workspace",
scopeKey,
queryScope: undefined,
queryFilter: {},
groupedScopeFilter: {},
loadMoreScope: undefined,
loadMoreFilter: undefined,
userId: undefined,
createDefaults: {},
};
}
case "project": {
const queryFilter = { project_id: scope.projectId };
return {
kind: "scoped",
scopeKey,
queryScope: scopeKey,
queryFilter,
groupedScopeFilter: queryFilter,
loadMoreScope: scopeKey,
loadMoreFilter: queryFilter,
userId: undefined,
createDefaults: { project_id: scope.projectId },
};
}
case "my": {
const plan = myRelationPlan(scope);
return {
kind: "scoped",
scopeKey,
...plan,
groupedScopeFilter: plan.queryFilter,
loadMoreScope: plan.queryScope,
loadMoreFilter: plan.queryFilter,
};
}
case "actor": {
const queryFilter =
scope.relation === "assigned"
? { assignee_id: scope.actorId }
: { creator_id: scope.actorId };
return {
kind: "scoped",
scopeKey,
queryScope: scopeKey,
queryFilter,
groupedScopeFilter: queryFilter,
loadMoreScope: scopeKey,
loadMoreFilter: queryFilter,
userId: undefined,
createDefaults:
scope.relation === "assigned"
? {
assignee_type: scope.actorType,
assignee_id: scope.actorId,
}
: {},
};
}
case "team":
throw new UnsupportedIssueScopeError(scope, "issue surface query plan");
}
}