Fix integration detail page 404 from route shadowing

[JadeCara]

Summary

• ENG-564 (ENG-564 (2/4): Node-based dataset editor with drill-down, CRUD, metadata editing, and YAML panel #7687) added pages/integrations/[id]/edit-dataset.tsx, which created a [id]/ directory alongside the existing [id].tsx dynamic route
• Next.js resolves directory routes over file routes, so the [id]/ directory shadows [id].tsx
• Since [id]/ has no index.tsx, all /integrations/<key> URLs (e.g. /integrations/testjirae2e) return a 404:

Error [PageNotFoundError]: Cannot find module for page: /integrations/testjirae2e
    at ignore-listed frames {
  code: 'ENOENT'
}
 GET /integrations/testjirae2e 404 in 322ms (next.js: 173ms, application-code: 150ms)

• Fix: Move [id].tsx → [id]/index.tsx so the detail page and nested routes (edit-dataset) coexist correctly

Test plan

• Navigate to any integration detail page (e.g. /integrations/<key>) — should load instead of 404
• Navigate to /integrations/<key>/edit-dataset — should still work
• Integration list page (/integrations) — unaffected

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
fides-plus-nightly	Ready	Preview, Comment	May 5, 2026 3:04pm

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
fides-privacy-center	Ignored		May 5, 2026 3:04pm

[JadeCara]

/code-review

[claude]

Code Review: PR #8103 — Fix integration detail route

Summary: This is a minimal, surgical fix. The change renames clients/admin-ui/src/pages/integrations/[id].tsx → clients/admin-ui/src/pages/integrations/[id]/index.tsx. No code is modified — it's a pure file move.

What the fix does

Next.js uses file-based routing. When ENG-564 added a nested route directory (e.g. integrations/[id]/some-child-route/), it created a conflict: Next.js cannot have both a [id].tsx file and a [id]/ directory at the same level — the directory wins, causing the [id].tsx page to effectively shadow out and return 404. Converting the file to [id]/index.tsx resolves the conflict while preserving the exact same URL (/integrations/:id).

Review findings

Correctness: The fix is correct. This is the standard Next.js pattern for converting a page file to a layout-compatible index route when a sibling directory with the same name is needed.

No logic changes: File content is 100% identical (similarity index 100%), so no functional regression is possible.

Changelog: A changelog entry is included and accurately describes the fix.

No concerns: No issues found. The change is minimal, well-scoped, and solves the reported 404 correctly.

---

🔬 Codegraph: connected (48932 nodes)

---

💡 Write /code-review in a comment to re-run this review.

[github-actions]

Title	Lines	Statements	Branches	Functions
admin-ui		6.57% (2975/45247)	5.86% (1525/25997)	4.64% (620/13345)
fides-js		79.43% (2013/2534)	66.13% (1244/1881)	73.09% (345/472)
privacy-center		85.97% (331/385)	81.36% (179/220)	78.87% (56/71)

[lucanovera]

I couldn't reproduce the original issue, but this is the correct way of organizing the files and it loads correctly after clearing the next.js cache. approved.