mirror of
https://github.com/alkimake/paperclip.git
synced 2026-06-18 03:30:39 +09:00
## Thinking Path > - Paperclip orchestrates AI agents for zero-human companies > - Operators rely on issue, inbox, and routine views to understand what the company is doing in real time > - Those views need to stay fast and readable even when issue lists, markdown comments, and run metadata get large > - The current branch had a coherent set of UI and live-update improvements spread across issue search, issue detail rendering, routine affordances, and workspace lookups > - This pull request groups those board-facing changes into one standalone branch that can merge independently of the heartbeat/runtime work > - The benefit is a faster, clearer issue and routine workflow without changing the underlying task model ## What Changed - Show routine execution issues by default and rename the filter to `Hide routine runs` so the default state no longer looks like an active filter. - Show the routine name in the run dialog and tighten the issue properties pane with a workspace link, copy-on-click behavior, and an inline parent arrow. - Reduce issue detail rerenders, keep queued issue chat mounted, improve issues page search responsiveness, and speed up issues first paint. - Add inbox "other search results", refresh visible issue runs after status updates, and optimize workspace lookups through summary-mode execution workspace queries. - Improve markdown wrapping and scrolling behavior for long strings and self-comment code blocks. - Relax the markdown sanitizer assertion so the test still validates safety after the new wrap-friendly inline styles. ## Verification - `pnpm vitest run ui/src/components/IssuesList.test.tsx ui/src/lib/inbox.test.ts ui/src/pages/Issues.test.tsx ui/src/context/BreadcrumbContext.test.tsx ui/src/context/LiveUpdatesProvider.test.ts ui/src/components/MarkdownBody.test.tsx ui/src/api/execution-workspaces.test.ts server/src/__tests__/execution-workspaces-routes.test.ts` ## Risks - This touches several issue-facing UI surfaces at once, so regressions would most likely show up as stale rendering, search result mismatches, or small markdown presentation differences. - The workspace lookup optimization depends on the summary-mode route shape staying aligned between server and UI. ## Model Used - OpenAI Codex, GPT-5-based coding agent in the Codex CLI environment. Exact backend model deployment ID was not exposed in-session. Tool-assisted editing and shell execution were used. ## 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) - [x] 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>
62 lines
1.9 KiB
TypeScript
62 lines
1.9 KiB
TypeScript
import { createContext, useCallback, useContext, useEffect, useState, type ReactNode } from "react";
|
|
|
|
export interface Breadcrumb {
|
|
label: string;
|
|
href?: string;
|
|
}
|
|
|
|
interface BreadcrumbContextValue {
|
|
breadcrumbs: Breadcrumb[];
|
|
setBreadcrumbs: (crumbs: Breadcrumb[]) => void;
|
|
mobileToolbar: ReactNode | null;
|
|
setMobileToolbar: (node: ReactNode | null) => void;
|
|
}
|
|
|
|
const BreadcrumbContext = createContext<BreadcrumbContextValue | null>(null);
|
|
|
|
function breadcrumbsEqual(left: Breadcrumb[], right: Breadcrumb[]) {
|
|
if (left === right) return true;
|
|
if (left.length !== right.length) return false;
|
|
for (let index = 0; index < left.length; index += 1) {
|
|
if (left[index]?.label !== right[index]?.label || left[index]?.href !== right[index]?.href) {
|
|
return false;
|
|
}
|
|
}
|
|
return true;
|
|
}
|
|
|
|
export function BreadcrumbProvider({ children }: { children: ReactNode }) {
|
|
const [breadcrumbs, setBreadcrumbsState] = useState<Breadcrumb[]>([]);
|
|
const [mobileToolbar, setMobileToolbarState] = useState<ReactNode | null>(null);
|
|
|
|
const setBreadcrumbs = useCallback((crumbs: Breadcrumb[]) => {
|
|
setBreadcrumbsState((current) => (breadcrumbsEqual(current, crumbs) ? current : crumbs));
|
|
}, []);
|
|
|
|
const setMobileToolbar = useCallback((node: ReactNode | null) => {
|
|
setMobileToolbarState(node);
|
|
}, []);
|
|
|
|
useEffect(() => {
|
|
if (breadcrumbs.length === 0) {
|
|
document.title = "Paperclip";
|
|
} else {
|
|
const parts = [...breadcrumbs].reverse().map((b) => b.label);
|
|
document.title = `${parts.join(" · ")} · Paperclip`;
|
|
}
|
|
}, [breadcrumbs]);
|
|
|
|
return (
|
|
<BreadcrumbContext.Provider value={{ breadcrumbs, setBreadcrumbs, mobileToolbar, setMobileToolbar }}>
|
|
{children}
|
|
</BreadcrumbContext.Provider>
|
|
);
|
|
}
|
|
|
|
export function useBreadcrumbs() {
|
|
const ctx = useContext(BreadcrumbContext);
|
|
if (!ctx) {
|
|
throw new Error("useBreadcrumbs must be used within BreadcrumbProvider");
|
|
}
|
|
return ctx;
|
|
}
|