ui/client/features/pages-editor/hooks/useFileFindings

Cockpit client (features), next. Source: ui/client/features/pages-editor/hooks/useFileFindings.tsx.

Type Aliases#

FileFindings#

FileFindings = { ok: true; ready: false; } | { findings: Finding[]; ok: true; ready: true; } | { error: string; ok: false; }

Defined in: ui/client/features/pages-editor/hooks/useFileFindings.tsx:6

Functions#

useFileFindings()#

useFileFindings(relPath): FileFindings | null

Defined in: ui/client/features/pages-editor/hooks/useFileFindings.tsx:13

Inspector "Findings" section: the SAME Review data (prHealth via /api/review), filtered to the open page file's path (as resolved by useImpact's /api/pages/impact, not recomputed here) -- no new findings engine. Deliberately never calls requestAnalysis the way the Review screen's own hooks (useReviewList/useReviewChange) do: opening a page in the Pages editor must not silently kick off a background PR-health run. ready: false is the honest "this file hasn't been reviewed yet" state, not an error.

Parameters#

relPath

string | null

Returns#

FileFindings | null