Files
paperclip/ui/src/hooks/useProjectOrder.ts
T
Dotta e89076148a [codex] Improve workspace runtime and navigation ergonomics (#3680)
## Thinking Path

> - Paperclip orchestrates AI agents for zero-human companies
> - That operator experience depends not just on issue chat, but also on
how workspaces, inbox groups, and navigation state behave over
long-running sessions
> - The current branch included a separate cluster of workspace-runtime
controls, inbox grouping, sidebar ordering, and worktree lifecycle fixes
> - Those changes cross server, shared contracts, database state, and UI
navigation, but they still form one coherent operator workflow area
> - This pull request isolates the workspace/runtime and navigation
ergonomics work into one standalone branch
> - The benefit is better workspace recovery and navigation persistence
without forcing reviewers through the unrelated issue-detail/chat work

## What Changed

- Improved execution workspace and project workspace controls, request
wiring, layout, and JSON editor ergonomics
- Hardened linked worktree reuse/startup behavior and documented the
`worktree repair` flow for recovering linked worktrees safely
- Added inbox workspace grouping, mobile collapse, archive undo,
keyboard navigation, shared group-header styling, and persisted
collapsed-group behavior
- Added persistent sidebar order preferences with the supporting DB
migration, shared/server contracts, routes, services, hooks, and UI
integration
- Scoped issue-list preferences by context and added targeted UI/server
tests for workspace controls, inbox behavior, sidebar preferences, and
worktree validation

## Verification

- `pnpm vitest run
server/src/__tests__/sidebar-preferences-routes.test.ts
ui/src/pages/Inbox.test.tsx
ui/src/components/ProjectWorkspaceSummaryCard.test.tsx
ui/src/components/WorkspaceRuntimeControls.test.tsx
ui/src/api/workspace-runtime-control.test.ts`
- `server/src/__tests__/workspace-runtime.test.ts` was attempted, but
the embedded Postgres suite self-skipped/hung on this host after
reporting an init-script issue, so it is not counted as a local pass
here

## Risks

- Medium: this branch includes migration-backed preference storage plus
worktree/runtime behavior, so merge review should pay attention to state
persistence and worktree recovery semantics
- The sidebar preference migration is standalone, but it should still be
watched for conflicts if another migration lands first

## Model Used

- OpenAI Codex coding agent (GPT-5-class runtime in Codex CLI; exact
deployed model ID is not exposed in this environment), reasoning
enabled, tool use and local code execution enabled

## Checklist

- [x] I have included a thinking path that traces from project context
to this change
- [x] I have specified the model used (with version and capability
details)
- [ ] I have run tests locally and they pass
- [x] I have added or updated tests where applicable
- [ ] If this change affects the UI, I have included before/after
screenshots
- [x] I have updated relevant documentation to reflect my changes
- [x] I have considered and documented any risks above
- [x] I will address all Greptile and reviewer comments before
requesting merge

---------

Co-authored-by: Paperclip <noreply@paperclip.ing>
2026-04-14 12:57:11 -05:00

86 lines
2.8 KiB
TypeScript

import { useCallback, useEffect, useMemo, useState } from "react";
import { useMutation, useQuery, useQueryClient } from "@tanstack/react-query";
import type { Project } from "@paperclipai/shared";
import { sidebarPreferencesApi } from "../api/sidebarPreferences";
import { sortProjectsByStoredOrder } from "../lib/project-order";
import { queryKeys } from "../lib/queryKeys";
type UseProjectOrderParams = {
projects: Project[];
companyId: string | null | undefined;
userId: string | null | undefined;
};
function areEqual(a: string[], b: string[]) {
if (a.length !== b.length) return false;
for (let i = 0; i < a.length; i += 1) {
if (a[i] !== b[i]) return false;
}
return true;
}
function buildOrderIds(projects: Project[], orderedIds: string[]) {
return sortProjectsByStoredOrder(projects, orderedIds).map((project) => project.id);
}
export function useProjectOrder({ projects, companyId, userId }: UseProjectOrderParams) {
const queryClient = useQueryClient();
const queryKey = useMemo(
() => queryKeys.sidebarPreferences.projectOrder(companyId ?? "__none__", userId ?? "__anon__"),
[companyId, userId],
);
const { data } = useQuery({
queryKey,
queryFn: () => sidebarPreferencesApi.getProjectOrder(companyId!),
enabled: Boolean(companyId && userId),
});
const [orderedIds, setOrderedIds] = useState<string[]>(() => {
return buildOrderIds(projects, []);
});
useEffect(() => {
const nextIds = buildOrderIds(projects, data?.orderedIds ?? []);
setOrderedIds((current) => (areEqual(current, nextIds) ? current : nextIds));
}, [data?.orderedIds, projects]);
const mutation = useMutation({
mutationFn: (nextIds: string[]) => sidebarPreferencesApi.updateProjectOrder(companyId!, { orderedIds: nextIds }),
onSuccess: (preference) => {
queryClient.setQueryData(queryKey, preference);
},
});
const orderedProjects = useMemo(
() => sortProjectsByStoredOrder(projects, orderedIds),
[projects, orderedIds],
);
const persistOrder = useCallback(
(ids: string[]) => {
const idSet = new Set(projects.map((project) => project.id));
const filtered = ids.filter((id) => idSet.has(id));
for (const project of projects) {
if (!filtered.includes(project.id)) filtered.push(project.id);
}
setOrderedIds((current) => (areEqual(current, filtered) ? current : filtered));
if (!companyId || !userId) return;
queryClient.setQueryData(queryKey, (current: { orderedIds?: string[]; updatedAt?: Date | null } | undefined) => ({
orderedIds: filtered,
updatedAt: current?.updatedAt ?? null,
}));
mutation.mutate(filtered);
},
[companyId, mutation, projects, queryClient, queryKey, userId],
);
return {
orderedProjects,
orderedIds,
persistOrder,
};
}