[itsmiso-ai]

What

Replaces all untyped any casts in src/app/projects/page.tsx with the properly typed Issue interface from @/types. Specifically: imports Issue, types filter/map callback parameters as Issue, and removes i as any and (statusIssues as any) casts.

Why

T…

Fixes #620

Opened by foreman on review GO (workload wl-misospace-dispatch-620).

[itsmiso-ai]

⚠️ This PR fix item has been marked as BLOCKED and needs human attention.

Reason: Review comment on src/app/projects/page.tsx:4

Latest note: foreman fix Workload prfix-misospace-dispatch-731 succeeded but PR is still not mergeable after 3/3 attempts

Posted automatically by Dispatch on 2026-08-06T20:30:07.014Z

Superseded by a newer automated review for this pull request.

Superseded by a newer automated review for this pull request.

[its-saffron]

AI Automated Review

Full PR review.

Analysis engine: dsv4f@https://litellm.jory.dev/v1 (openai) — primary route

Recommendation: Approve

This is a small, focused type-safety cleanup that directly matches its linked issue (PR 620). Both any casts in src/app/projects/page.tsx are removed in favor of a new IssueWithRepo type, and all CI checks (Build, Typecheck, Lint, Tests, Docker Build, npm audit) are green on head commit a5102cb. No behavioral change.

Change-by-change findings

1. src/types/index.ts — Adds IssueWithRepo extends Omit<Issue, "repository"> { repository: Repository }. Structurally sound: Repository supplies the fullName/name fields required by groupIssuesByProject, and Omit<Issue, "repository"> avoids a conflicting duplicate key with the base Issue.repository partial shape ({ fullName: string }). The JSDoc accurately describes the projects page fetch with include: { repository: true }.

2. src/app/projects/page.tsx — Adds a type-only import and annotates the filter/map callbacks as IssueWithRepo, replacing (i: any) => getProjectIssueStatus(i as any) === column.id and (statusIssues as any).map((issue: any) => ...). IssueWithRepo satisfies the { labels: string[]; state: string } parameter type of getProjectIssueStatus, so the as any casts are no longer needed. The file is now free of any casts (the remaining Record<string, unknown> in getProjects is unknown, not any).

• CI verification: The Typecheck check succeeded on this exact commit. Under strict function typing, that also structurally validates that the Prisma payload from issue.findMany({ include: { repository: true } }) is assignable to IssueWithRepo — including the full Repository shape (id, name, owner, fullName, enabled).

Sources

• src/app/projects/page.tsx (full file read)
• src/types/index.ts (full file read)
• src/lib/projects.ts (getProjectIssueStatus, groupIssuesByProject signatures)
• CI status for commit a5102cb (Docker Build, Build, Typecheck, Lint, Tests, npm audit, review — all success)
• GitHub issue PR 620 body (acceptance criteria)

Standards Compliance

• AGENTS.md requires lint/typecheck to pass and blocks CI on them — both are green here.
• The new type is imported with import type, matching the convention that types with no runtime existence are type-only imports.
• No schema, migration, environment-variable, or secret-related changes; the change is UI/type-only, so the Prisma and environment conventions in AGENTS.md are unaffected.
• Label/status helpers (BOARD_COLUMNS, STATUS_LABELS, getProjectIssueStatus) are reused as-is; no duplicated or hardcoded label logic was introduced.

Linked Issue Fit

Issue PR 620 ("Remove pervasive as any casts in projects page"):

• Problem statement: the issue cites (i: any) => getProjectIssueStatus(i as any) and (statusIssues as any).map((issue: any) => ...) — both cited casts are removed by this diff.
• Acceptance criteria: "Replace all any references with a properly typed IssueWithRepo or comparable interface, verified by npx tsc --noEmit." — the PR introduces exactly IssueWithRepo (the issue-suggested name), applies it to both call sites, and the repository's Typecheck CI step passes on the head commit.
• The issue is labeled status/in-review, consistent with this PR being reviewable; no acceptance criterion is missing or misinterpreted.

Note (non-blocking): the PR description says it imports Issue and types the callbacks as Issue, but the diff actually introduces and uses IssueWithRepo. The code is aligned with the issue's acceptance criteria; only the PR body text is stale.

[its-saffron]

Info (docs): PR description states the change imports and uses Issue, but the diff actually introduces and uses IssueWithRepo; the code matches issue PR 620's acceptance criteria, so only the PR body text is stale.

Automated finding from AI PR review.