diff --git a/frontend/app/(admin)/admin/doc-control/drawings/contract/categories/page.tsx b/frontend/app/(admin)/admin/doc-control/drawings/contract/categories/page.tsx
index 557b336..16b8076 100644
--- a/frontend/app/(admin)/admin/doc-control/drawings/contract/categories/page.tsx
+++ b/frontend/app/(admin)/admin/doc-control/drawings/contract/categories/page.tsx
@@ -1,6 +1,6 @@
'use client';
-import { useState } from 'react';
+import React, { useState } from 'react';
import { GenericCrudTable } from '@/components/admin/reference/generic-crud-table';
import { ColumnDef } from '@tanstack/react-table';
import { Select, SelectContent, SelectItem, SelectTrigger, SelectValue } from '@/components/ui/select';
@@ -120,19 +120,6 @@ export default function ContractCategoriesPage() {
filters={projectFilter}
/>
- {/*
- Note: For mapping, we should ideally have a separate "Mappings" column or action button.
- Since GenericCrudTable might not support custom action columns easily without modification,
- we are currently just listing categories. To add mapping functionality, we might need
- to either extend GenericCrudTable or create a dedicated page for mappings.
-
- Given the constraints, I will add a "Mapped Sub-categories" management section
- that opens when clicking a category ROW or adding a custom action if GenericCrudTable supports it.
- For now, let's assume we need to extend GenericCrudTable or replace it to support this specific requirement.
-
- However, to keep it simple and consistent:
- Let's add a separate section below the table or a dialog triggered by a custom cell.
- */}
+ );
+ }
+ return this.props.children;
+ }
+}
+
function CategoryMappingSection({ projectId }: { projectId: number }) {
- // ... logic to manage mappings would go here ...
- // But to properly implement this, we need a full mapping UI.
- // Let's defer this implementation pattern to a separate component to keep this file clean
- // and just mount it here.
return (
Category Mappings (Map Sub-categories to Categories)
Select a category to view and manage its sub-categories.
- {/*
- Real implementation would be complex here.
- Better approach: Add a "Manage Sub-categories" button to the Categories table if possible.
- Or simpler: A separate "Mapping" page.
- */}
-
+
+
+
diff --git a/frontend/build_output.txt b/frontend/build_output.txt
new file mode 100644
index 0000000..e0a4cd8
--- /dev/null
+++ b/frontend/build_output.txt
@@ -0,0 +1,22 @@
+[baseline-browser-mapping] The data in this module is over two months old. To ensure accurate Baseline data, please update: `npm i baseline-browser-mapping@latest -D`
+ Γû▓ Next.js 16.0.7 (Turbopack)
+ - Environments: .env.local
+
+ ΓÜá The "middleware" file convention is deprecated. Please use "proxy" instead. Learn more: https://nextjs.org/docs/messages/middleware-to-proxy
+ Creating an optimized production build ...
+[baseline-browser-mapping] The data in this module is over two months old. To ensure accurate Baseline data, please update: `npm i baseline-browser-mapping@latest -D`
+ Γ£ô Compiled successfully in 7.5s
+ Running TypeScript ...
+Failed to compile.
+
+.next/dev/types/validator.ts:53:39
+Type error: Cannot find module '../../../app/(admin)/admin/audit-logs/page.js' or its corresponding type declarations.
+
+ 51 | {
+ 52 | type __IsExpected> = Specific
+> 53 | const handler = {} as typeof import("../../../app/(admin)/admin/audit-logs/page.js")
+ | ^
+ 54 | type __Check = __IsExpected
+ 55 | // @ts-ignore
+ 56 | type __Unused = __Check
+Next.js build worker exited with code: 1 and signal: null