Compare commits

..

9 Commits

29 changed files with 894 additions and 284 deletions

18
.agent/profile.yml Normal file
View File

@@ -0,0 +1,18 @@
schema_version: 1
project:
id: kfpa-cx-dash-front
name: KFPA CX Dashboard Frontend
type: requested-project
layer: frontend
legacy: false
stack:
- typescript
- react
- nextjs
shared_contracts:
consumes:
- kri-front-common
- kri-ui-registry

20
.agent/project.md Normal file
View File

@@ -0,0 +1,20 @@
## KFPA CX Dashboard Frontend Repository Rules
### Deliverable and User Experience
- This Next.js frontend visualizes KFPA CSI summaries, ranks, business and object-type comparisons, comments, and related survey results.
- Treat approved planning and acceptance material as the scope boundary. Preserve section navigation, survey-date context, filters, labels, chart/table values, rankings, comment workflows, and export behavior.
- A visual change must not silently alter the represented score, denominator, rank, tie handling, ordering, rounding, tooltip meaning, or empty-data behavior.
- Keep customer survey data, comments, exported workbooks, and planning material out of logs, fixtures, screenshots, and external services.
### Frontend Implementation
- Use the consumed KRI frontend common and UI registry contracts. Prefer an existing shadcn/ui or registry component before creating a new foundational component.
- Do not create new TypeScript type or interface names ending in `Dto` or `DTO`.
- Preserve accessibility, responsive layout, loading, empty, error, unauthorized, confirmation, success, and administrative-edit states.
- Coordinate API request, response, authentication, statistics, comment, and error changes with the backend without requiring an unsafe simultaneous deployment.
### Harness and Verification
- `AGENTS.md` and `CLAUDE.md` are generated. Edit `.agent/profile.yml` or `.agent/project.md`, then recompose instead of editing generated files.
- Use existing npm scripts and focused lint, type-check, test, or production build checks. Do not call production APIs, modify real comments, or export customer data during validation.

View File

@@ -3,3 +3,4 @@ NEXT_PUBLIC_API_BASE=https://test-kfpa-dash.kric.com/api
ENV=prod
API_BACK_SERVER=http://127.0.0.1:6103/api/v1
IP_WHITELIST=127.0.0.1,::1,211.37.10.198,211.254.145.130,1.235.195.3

View File

@@ -3,3 +3,4 @@ NEXT_PUBLIC_API_BASE=http://localhost:6102/api
ENV=local
API_BACK_SERVER=http://localhost:6103/api/v1
IP_WHITELIST=127.0.0.1,::1

View File

@@ -3,3 +3,4 @@ NEXT_PUBLIC_API_BASE=https://kfpa-dash.kric.com/api
ENV=prod
API_BACK_SERVER=http://127.0.0.1:6103/api/v1
IP_WHITELIST=127.0.0.1,::1,211.37.10.198,211.254.145.130,1.235.195.3

4
.gitattributes vendored Normal file
View File

@@ -0,0 +1,4 @@
/.gitattributes text eol=lf
/.agent/** text eol=lf
/AGENTS.md text eol=lf
/CLAUDE.md text eol=lf

306
AGENTS.md Normal file
View File

@@ -0,0 +1,306 @@
<!--
GENERATED BY KRI AGENT HARNESS. DO NOT EDIT DIRECTLY.
Project: kfpa-cx-dash-front
Schema version: 1
Edit the source fragments or repository .agent files, then recompose.
-->
# KRI Development Base Instructions
This document defines the shared working rules for KRI development repositories.
Keep project-specific facts and commands in the project profile and project rules.
## Instruction Resolution
Apply repository instructions in this order:
1. Base rules
2. Project-type rules
3. Technology-stack rules
4. Shared consumer contracts
5. Project-specific rules
6. The explicitly approved task scope
Later and more specific instructions may override earlier general instructions only within their stated scope.
- Apply a shared consumer contract only when `.agent/profile.yml` declares it.
- Do not silently resolve a material instruction conflict. Report the conflicting rules and request a decision before changing files.
- Rules involving destructive actions, credentials, external systems, production, deployment, databases, or Git publication require explicit authorization even when a later rule is less restrictive.
## Communication
- Respond to the user in Korean unless the user requests another language.
- Keep code identifiers, commands, paths, protocol names, and external API terms in their original form.
- Follow the repository's existing language conventions for code comments and user-facing messages.
- Lead with the result or decision, then provide only the detail needed to verify it.
- Do not create or retain a full session transcript.
## Work Authorization
- The default workflow is discussion first and explicit execution approval second.
- During discussion, perform only read-only investigation needed to understand the task and propose a concrete plan, unless the user prohibits inspection.
- Read-only investigation may include file inspection, code search, encoding checks, `git status`, `git diff`, `git log`, and sanitized official-documentation lookup.
- Before execution approval, do not edit files, install dependencies, run builds or tests, start services, connect to databases, or change local or external state.
- Before requesting approval, describe the intended scope, affected areas, validation plan, and material risks.
- Treat approval as limited to the presented scope. Pause and discuss again if the work materially expands.
- If the user explicitly requests immediate execution without prior discussion, the discussion gate may be skipped for the stated scope.
- Fast-track authorization does not implicitly authorize protected operations such as destructive commands, production changes, deployments, database mutations, Git publication, or external messages.
## Local Development Environment
- Primary OS: Windows 11.
- Primary shell: PowerShell.
- Use Git Bash only when the repository already depends on Bash or POSIX shell behavior.
- Prefer repository-provided wrappers and scripts over globally installed commands.
- Do not assume that GNU utilities, WSL, Docker, or a Unix-compatible shell are available unless the project profile confirms them.
- Detect Java, Node.js, .NET, Python, package-manager, and database-tool versions from repository configuration.
- Do not install or modify global toolchains as part of a project task.
Preferred human-facing tools:
- Classic ASP: Visual Studio Code
- Java and Spring Boot: IntelliJ IDEA
- C# and .NET: JetBrains Rider
- JavaScript, TypeScript, and Next.js: JetBrains WebStorm
- Python: JetBrains PyCharm
- Microsoft SQL Server: SQL Server Management Studio
- Other databases: JetBrains DataGrip
- These preferences do not authorize launching or controlling a GUI application.
- Prefer IDE-independent commands that can also run in CI.
- Do not modify global IDE settings.
- Do not create or modify `.idea`, `.vscode`, workspace, or run-configuration files unless the approved task requires it.
- Preserve existing shared IDE configuration when it is already tracked.
## PowerShell and Path Safety
- Quote paths containing spaces, brackets, parentheses, Korean characters, or PowerShell metacharacters.
- Prefer `-LiteralPath` when operating on an exact filesystem path.
- Use project-relative paths in committed configuration and documentation. Do not commit machine-specific paths such as `D:\_____Dev\...`.
- Do not pass filesystem targets between PowerShell, `cmd.exe`, and Bash for destructive or recursive operations.
- Keep a filesystem operation within one shell from target resolution through execution.
- Before a recursive delete or move, resolve and verify every absolute target.
- Never use a drive root, workspace root, user profile, unresolved variable, wildcard, or broad glob as a recursive delete target.
- Prefer recoverable operations when practical.
## Change Discipline
- Preserve all existing user changes, including uncommitted and untracked work.
- Keep changes minimal but complete for the approved objective.
- Avoid unrelated cleanup, formatting, renaming, dependency upgrades, and architectural refactoring.
- Do not overwrite or revert unrelated changes.
- Stop and report when the requested change overlaps existing work in a way that cannot be handled safely.
- Prefer changing an authoritative source over editing generated output.
- Treat files marked as generated as read-only unless regeneration is part of the approved plan.
- Do not edit vendored dependencies, build outputs, caches, or generated clients unless explicitly required.
- Do not regenerate a broad set of files for a narrow change without first explaining the expected output scope.
## Text Encoding and Korean Content Safety
- Treat the existing file encoding, BOM state, and line-ending style as part of the file's contract.
- Preserve Korean comments, user-facing messages, error messages, identifiers, and documentation exactly unless the task explicitly requires changing them.
- Do not assume that garbled terminal output means the file itself is corrupted. Verify bytes and encoding before modifying suspicious text.
- Before editing an existing text file, determine its current encoding and BOM state when repository configuration does not already guarantee them.
- Do not convert encoding, add or remove a BOM, or normalize line endings as a side effect of an unrelated change.
- Avoid whole-file rewrites for small changes.
- Do not rewrite source files through `Get-Content | Set-Content`, `Out-File`, shell redirection, or another method whose encoding behavior is implicit.
- Do not use a patching or formatting tool on a non-UTF-8 file unless it is known to preserve that file's encoding.
- Treat a console display problem and an on-disk encoding problem as separate issues.
- After editing Korean text, inspect the diff for replacement characters (`<60>`), mojibake, unexpected escapes, BOM changes, and unrelated line-ending changes.
- Run `.agent/tools/check-encoding.ps1` when it is available and the change touches Korean text or a non-default encoding.
- If encoding cannot be identified confidently, stop before writing and report the affected file and evidence.
- For a new text file, follow repository configuration. If no rule exists, use UTF-8 without BOM.
## Git Safety
- Use `git status`, `git diff`, and `git log` for read-only investigation.
- Do not run `commit`, `push`, `pull`, `fetch`, `merge`, `rebase`, `reset`, `checkout`, `switch`, `stash`, `clean`, `tag`, or force operations unless that specific operation is explicitly approved.
- Source-edit approval does not include commit or push approval.
- Never amend an existing commit unless explicitly requested.
- Before an approved commit, show the intended files, validation results, and proposed commit message.
- Never push directly to a protected branch unless the user names the target branch and explicitly authorizes the push.
## Dependencies and External Actions
- Use the package manager, lockfile, and toolchain already selected by the repository.
- Do not install global packages.
- Do not add, remove, or upgrade a dependency unless it was included in the approved plan.
- Pause for approval if an unplanned dependency becomes necessary.
- Keep lockfiles synchronized with approved dependency changes.
- Do not deploy, publish packages, create releases, send messages or email, call business APIs, or modify external services unless explicitly requested.
- Never upload proprietary source code, internal documents, credentials, customer data, or database contents to an external service.
- Remove secrets and unnecessary internal identifiers from external search queries.
## Database Safety
- Treat writing or reviewing SQL as source code separately from executing SQL against a database.
- SQL files, migrations, schema proposals, and query drafts may be created within an approved source-change scope.
- Do not connect to a shared, staging, or production database without explicit authorization for that environment.
- Read-only queries against a non-local database also require authorization because results may contain sensitive data.
- Do not execute DDL, DML, stored procedures, migrations, administrative commands, or data-correction scripts against a non-disposable database without separate authorization for the exact target and operation.
- Source-change approval does not authorize migration execution.
- Use a disposable local or test database for approved validation only after verifying its identity and disposable nature.
- Never place credentials, connection strings, or sensitive query results in source files, logs, generated documents, or chat output.
## Secrets and Sensitive Data
- Never add credentials, tokens, passwords, private keys, connection strings, session identifiers, or production data to source control.
- Read sensitive files only when the approved task requires it and no safer source exists.
- Prefer inspecting configuration keys and schemas without displaying secret values.
- Never echo secrets into terminal output, chat responses, logs, diffs, generated documents, test fixtures, or screenshots.
- Redact sensitive values when reporting errors or command output.
- If a possible secret is discovered, do not repeat it. Report only its location, type, and recommended containment action.
- Do not rotate, revoke, copy, or otherwise modify credentials unless that exact action is explicitly authorized.
## Validation
- Discover supported build, test, lint, type-check, and formatting commands from repository files and project instructions. Do not invent commands.
- Include intended validation in the discussion-phase plan.
- After approved changes, run the narrowest relevant validation first, then broader checks when appropriate.
- Limit formatting to files within the approved scope.
- Do not run tests that require a shared database, production service, paid external API, or sensitive data unless separately authorized.
- Do not claim that a check passed unless it was executed successfully.
- If a check cannot be run, state the exact reason.
- Distinguish a current-change failure from a pre-existing failure or an undetermined failure.
- Do not fix unrelated failures without expanding the approved scope.
- Inspect the worktree after validation for unexpected generated files, formatting churn, encoding changes, or lockfile changes.
## Artifacts and Session Records
- Do not create full-session transcripts, automatic HTML copies, analysis reports, or extra documentation unless explicitly requested.
- Store durable information in the repository's existing documentation structure.
- Do not place generated reports or temporary analysis files in the repository root.
- Remove task-specific temporary files created by the current task after validation when removal is safe.
## Completion Report
When implementation is complete, report in Korean:
- what changed and why;
- the main affected files or components;
- validation commands actually executed and their results;
- checks not executed and the reason;
- remaining risks, assumptions, or follow-up work;
- database, deployment, dependency, encoding, and compatibility impact when applicable.
- Do not report completion while required validation is failing or known encoding corruption is unresolved.
- Keep the report concise and do not include a full session transcript.
## Requested Project Rules
- Treat the approved requirements, acceptance criteria, and recorded decisions as the primary scope boundary.
- Do not infer a requirement solely from a file name, folder date, or apparently newer document.
- When requirements conflict, report the exact sources and request a decision.
- Preserve original customer, partner, and planning documents as read-only evidence unless document editing is explicitly approved.
- Summarize durable implementation requirements inside the repository rather than relying only on files outside the repository.
- Do not expand the deliverable with speculative features, infrastructure, or architectural changes.
- Record material assumptions and unresolved decisions in the project-specific rules or existing project documentation.
- Define observable acceptance criteria before implementation.
- Treat separately managed Frontend and Backend repositories as independent deliverables with a coordinated contract.
- Protect customer, partner, survey, and field data as sensitive information.
- Keep handoff, operation, configuration, and validation instructions usable by the requesting team.
- Report deviations from the requested scope and obtain approval before proceeding.
## TypeScript
- Treat the repository's current TypeScript version, `tsconfig` files, module system, path aliases, and package manager as authoritative.
- Preserve or strengthen existing strictness. Do not weaken compiler options or hide errors with broad `any`, `@ts-ignore`, or unsafe assertions.
- Prefer narrow domain types, discriminated unions, and explicit boundary types over duplicated or overly generic shapes.
- Validate untrusted runtime input even when a compile-time type exists.
- Keep imports, exports, aliases, and generated-code boundaries consistent with the repository.
- Do not introduce a JavaScript-to-TypeScript conversion outside the approved scope.
- Run the repository's focused type-check, lint, test, and build commands as applicable.
## React
- Treat the current React version, component style, state management, routing, styling, and test approach as authoritative.
- Do not perform unrelated class-to-hook, JavaScript-to-TypeScript, state-library, styling-system, or React-to-Next.js migrations.
- Keep components focused and follow the repository's established split between presentation, state, data access, and side effects.
- Keep effects dependency-correct and clean up subscriptions, timers, listeners, and in-flight work where applicable.
- Use stable semantic keys and preserve accessibility, loading, empty, error, disabled, and success states.
- Preserve public component props and shared UI contracts unless a coordinated breaking change is explicitly approved.
- Treat any planned Next.js migration as a separate policy and task; the current React application remains authoritative until that migration slice is approved.
## Next.js
- Treat the repository's current Next.js and React versions, routing model, rendering model, and package manager as authoritative.
- Preserve server and client component boundaries. Add `use client` only when browser APIs, state, effects, or client-only libraries require it.
- Keep secrets, privileged data access, and server-only modules out of client bundles.
- Preserve established route, layout, middleware, authentication, authorization, caching, revalidation, and error-handling conventions.
- Validate request parameters, payloads, headers, cookies, and external responses at runtime.
- Do not create new frontend TypeScript type or interface names ending in `Dto` or `DTO`. Use domain- or purpose-specific names such as `User`, `UserInput`, `UserRequest`, or `UserResponse`; do not rename existing types solely to enforce this rule outside the approved scope.
- Use the approved KRI frontend and UI contracts when the project profile includes them; do not copy shared implementations into an application.
- Avoid incidental routing-model or rendering-strategy migrations.
- Run the repository's focused lint, type-check, test, and production build commands as applicable.
## KriFrontCommon Consumer Contract
### Package Usage
- Consume this contract through the published `@kri/common` package and only through entry points declared in its `package.json` `exports` map.
- Use the package root for runtime-neutral object, URL, date, string, and shared type utilities.
- Use a focused subpath such as `@kri/common/http`, `@kri/common/browser`, `@kri/common/server`, `@kri/common/security`, `@kri/common/hooks`, `@kri/common/query`, `@kri/common/config`, `@kri/common/jotai`, or `@kri/common/noti-hub` for the corresponding capability.
- Do not import from `@kri/common/src/*`, `@kri/common/dist/*`, or another undeclared deep path.
- Do not copy or fork a shared utility locally merely to avoid using an available public entry point. Propose a backward-compatible library addition when the shared contract is genuinely missing.
### Runtime and Optional Integrations
- Keep browser, server, and runtime-neutral imports on their intended side of the application boundary.
- A consumer that uses React hooks, TanStack Query, or Jotai integrations must provide the compatible optional peer dependency required by its selected entry point.
- Preserve the project's established HTTP client, authentication, error-policy, query-client, storage, and environment conventions when adopting a shared helper.
- Validate external data at runtime; a shared TypeScript type alone does not validate an API response or persisted value.
- Prefer named public exports and retain the consumer project's current module system and bundler conventions.
### Change Safety
- Pin or constrain the package version according to the consumer repository's dependency policy and commit its lockfile changes.
- Review release notes and the actual affected API before upgrading. Run the consumer's focused type-check, test, and build commands after an upgrade.
- Do not modify KriFrontCommon or another consumer repository unless it is explicitly included in the approved task scope.
## KriUiRegistry Consumer Contract
### UI Component Selection
When implementing or changing frontend UI, use this order:
1. Reuse an existing shared component in the project when it already meets the requirement.
2. Prefer an approved component from KriUiRegistry.
3. Otherwise, prefer a suitable shadcn/ui component.
4. Create a new custom component only when the preceding options cannot meet the requirement without an unsafe or misleading adaptation.
### Installation and Ownership
- Inspect the registry item and its dependencies before installation. Use the shadcn CLI with the approved registry endpoint under `https://ui-registry.kric.com/r/` instead of copying files from `dist/r` manually.
- `kri-data-table` uses the TanStack Table v8 API. Keep `@tanstack/react-table` within the supported `^8.21.3` range and do not upgrade it to v9 until KriUiRegistry provides an explicitly migrated component contract.
- Respect the consumer project's component aliases, target paths, package manager, styling system, React version, and existing design tokens.
- The shadcn workflow copies component source into the consumer repository. After installation, treat that copy as project-owned code; do not assume registry updates propagate automatically.
- Do not overwrite an existing project component without reviewing the diff and confirming that local behavior and accessibility are preserved.
- Keep package and lockfile changes produced by an installation within the approved scope.
### Adaptation and Verification
- Adapt business data and application behavior outside the shared component when possible. Avoid embedding project-specific API, route, authentication, or environment logic into a reusable component.
- Preserve the installed component's public props, accessibility, keyboard behavior, responsive layout, and loading, empty, error, and disabled states unless the task explicitly changes them.
- If the registry lacks a generally reusable capability, propose it in KriUiRegistry; do not modify that repository unless it is explicitly in scope.
- Run the consumer repository's focused type-check, lint, tests, and build after installation or upgrade.
## KFPA CX Dashboard Frontend Repository Rules
### Deliverable and User Experience
- This Next.js frontend visualizes KFPA CSI summaries, ranks, business and object-type comparisons, comments, and related survey results.
- Treat approved planning and acceptance material as the scope boundary. Preserve section navigation, survey-date context, filters, labels, chart/table values, rankings, comment workflows, and export behavior.
- A visual change must not silently alter the represented score, denominator, rank, tie handling, ordering, rounding, tooltip meaning, or empty-data behavior.
- Keep customer survey data, comments, exported workbooks, and planning material out of logs, fixtures, screenshots, and external services.
### Frontend Implementation
- Use the consumed KRI frontend common and UI registry contracts. Prefer an existing shadcn/ui or registry component before creating a new foundational component.
- Do not create new TypeScript type or interface names ending in `Dto` or `DTO`.
- Preserve accessibility, responsive layout, loading, empty, error, unauthorized, confirmation, success, and administrative-edit states.
- Coordinate API request, response, authentication, statistics, comment, and error changes with the backend without requiring an unsafe simultaneous deployment.
### Harness and Verification
- `AGENTS.md` and `CLAUDE.md` are generated. Edit `.agent/profile.yml` or `.agent/project.md`, then recompose instead of editing generated files.
- Use existing npm scripts and focused lint, type-check, test, or production build checks. Do not call production APIs, modify real comments, or export customer data during validation.

1
CLAUDE.md Normal file
View File

@@ -0,0 +1 @@
@AGENTS.md

View File

@@ -14,6 +14,7 @@ const BridgePlatformPage = () => {
selectedDiv={selectedDiv}
viewSubTitle={false}
sectionTitleSuffix={COMMENT_TABLE_TITLE}
widthClassName="w-[1200px]"
/>;
};

View File

@@ -7,7 +7,7 @@ import CustomerSatisfactionDetail from "@/components/kfpa/CustomerSatisfactionDe
const ConsultingPage = () => {
const { selectedDiv } = useLayoutFilter();
return selectedDiv === "-1" ? <CustomerSatisfactionTotal /> : <CustomerSatisfactionDetail selectedDiv={selectedDiv} />;
return selectedDiv === "-1" ? <CustomerSatisfactionTotal /> : <CustomerSatisfactionDetail selectedDiv={selectedDiv} widthClassName="w-[1200px]"/>;
};
export default ConsultingPage;

View File

@@ -7,7 +7,7 @@ import CustomerSatisfactionDetail from "@/components/kfpa/CustomerSatisfactionDe
const FireInvestigationPage = () => {
const { selectedDiv } = useLayoutFilter();
return selectedDiv === "-1" ? <CustomerSatisfactionTotal /> : <CustomerSatisfactionDetail selectedDiv={selectedDiv} />;
return selectedDiv === "-1" ? <CustomerSatisfactionTotal /> : <CustomerSatisfactionDetail selectedDiv={selectedDiv} widthClassName="w-[1200px]"/>;
};
export default FireInvestigationPage;

View File

@@ -7,7 +7,7 @@ import CustomerSatisfactionDetail from "@/components/kfpa/CustomerSatisfactionDe
const InsuranceOperationsPage = () => {
const { selectedDiv } = useLayoutFilter();
return selectedDiv === "-1" ? <CustomerSatisfactionTotal /> : <CustomerSatisfactionDetail selectedDiv={selectedDiv} />;
return selectedDiv === "-1" ? <CustomerSatisfactionTotal /> : <CustomerSatisfactionDetail selectedDiv={selectedDiv} widthClassName="w-[1200px]"/>;
};
export default InsuranceOperationsPage;

View File

@@ -7,7 +7,12 @@ import CustomerSatisfactionDetail from "@/components/kfpa/CustomerSatisfactionDe
const SafetyInspectionPage = () => {
const { selectedDiv } = useLayoutFilter();
return selectedDiv === "-1" ? <CustomerSatisfactionTotal /> : <CustomerSatisfactionDetail selectedDiv={selectedDiv} />;
return selectedDiv === "-1"
? <CustomerSatisfactionTotal />
: <CustomerSatisfactionDetail
selectedDiv={selectedDiv}
//widthClassName="w-[1553px]"
/>;
};
export default SafetyInspectionPage;

View File

@@ -14,6 +14,7 @@ const UcisPage = () => {
selectedDiv={selectedDiv}
viewSubTitle={false}
sectionTitleSuffix={COMMENT_TABLE_TITLE}
widthClassName="w-[1200px]"
/>;
};

21
src/app/403/page.tsx Normal file
View File

@@ -0,0 +1,21 @@
import type { Metadata } from "next";
export const metadata: Metadata = {
title: "403 Forbidden",
};
const ForbiddenPage = () => {
return (
<main className="flex min-h-dvh items-center justify-center bg-background px-6">
<section className="w-full max-w-md border border-border bg-card p-8 text-center shadow-sm">
<p className="text-sm font-semibold text-primary">403</p>
<h1 className="mt-3 text-2xl font-bold text-foreground">외부에서 접속할 수 없습니다.</h1>
<p className="mt-4 text-sm leading-6 text-muted-foreground">
해당 사이트는 외부의 접근을 허용하지 않습니다.
</p>
</section>
</main>
);
};
export default ForbiddenPage;

View File

@@ -122,6 +122,8 @@
--kfpa-red-100: #f2a8b5;
--kfpa-red-50: #fae6ea;
--kfpa-null: #9a9a9a;
/* =============================
Surface
============================= */
@@ -357,6 +359,7 @@
.border-border { border-color: var(--border); }
.text-zero { color: var(--kfpa-black-150) !important; }
.text-null { color: var(--kfpa-null) !important; }
/* KFPA neutral scale */
.bg-black-600 { background-color: var(--kfpa-black-600) !important; }
@@ -410,6 +413,7 @@
.bg-csi { background-color: var(--kfpa-csi) !important; }
.bg-direct { background-color: var(--kfpa-direct) !important; }
.bg-indirect { background-color: var(--kfpa-indirect) !important; }
.bg-null { background-color: var(--kfpa-null) !important; }
/* =============================
Content Text Size Utilities
@@ -599,10 +603,11 @@
.kfpa-detail-table {
--kfpa-detail-table-head-height: 56px;
--kfpa-detail-table-row-height: 56px;
--kfpa-detail-comment-table-row-height: 112px;
}
.kfpa-detail-rank-table {
--kfpa-detail-table-row-height: 56px;
min-width: 285px !important;
}
@@ -618,6 +623,7 @@
}
.kfpa-detail-comment-table tbody td {
min-height: var(--kfpa-detail-comment-table-row-height);
vertical-align: top;
}

View File

@@ -15,8 +15,8 @@ const geistMono = Geist_Mono({
});
export const metadata: Metadata = {
title: "화재보험협회 대시보드",
description: "화재보험협회 CX 대시보드",
title: "고객 관점 성과관리 대시보드",
description: "고객 관점 성과관리 대시보드",
};
export default function RootLayout({

View File

@@ -35,9 +35,52 @@ type Props = {
position?: "top" | "insideTop" | "right" | "insideRight";
color?: string;
distance?: number;
minPositionValue?: number;
};
};
type ChartCallbackParam = {
data?: unknown;
value?: unknown;
axisValueLabel?: string;
name?: string;
marker?: string;
seriesName?: string;
};
const isRecord = (value: unknown): value is Record<string, unknown> =>
typeof value === "object" && value !== null && !Array.isArray(value);
const toChartCallbackParam = (value: unknown): ChartCallbackParam =>
isRecord(value) ? value : {};
const getActualValue = (param: unknown) => {
const data = toChartCallbackParam(param).data;
if (isRecord(data) && "actualValue" in data) {
return data.actualValue;
}
return toChartCallbackParam(param).value;
};
const createLabelPositionTooltip = (fmt: ValueFormatter): EChartsOption["tooltip"] => ({
trigger: "axis",
axisPointer: { type: "shadow" },
formatter: (params: unknown) => {
const items = (Array.isArray(params) ? params : [params]).map(toChartCallbackParam);
const title = items[0]?.axisValueLabel ?? items[0]?.name ?? "";
const lines = items.map((item) => {
const value = getActualValue(item);
const text = typeof value === "number" ? fmt(value) : value == null ? "-" : String(value);
return `${item.marker ?? ""}${item.seriesName} ${text}`;
});
return [title, ...lines].join("<br/>");
},
});
const VerticalBar = ({
data,
height,
@@ -58,21 +101,31 @@ const VerticalBar = ({
const option: EChartsOption = useMemo(() => {
const fmt = valueFormatter ?? ((v: number) => String(v));
const minPositionValue = labelOptions?.minPositionValue;
return {
color: palette,
tooltip: tooltip ?? createDefaultTooltip(fmt),
tooltip: tooltip ?? (typeof minPositionValue === "number" ? createLabelPositionTooltip(fmt) : createDefaultTooltip(fmt)),
legend: legend ?? createDefaultLegend(),
grid: grid ?? createDefaultGrid(),
xAxis: xAxis ?? createCategoryAxis(data.categories, false, { axisTick: { alignWithLabel: true } }),
yAxis: yAxis ?? createValueAxis(),
series: data.series.map((s, index) => {
const showLabel = getIsShowLabel(showFocusLabel, index, data.series.length);
const seriesData = s.data.map((value) =>
typeof minPositionValue === "number" &&
typeof value === "number" &&
Number.isFinite(value) &&
value > 0.00 &&
value < minPositionValue
? { value: minPositionValue, actualValue: value }
: value
);
return {
name: s.name,
type: "bar",
data: s.data,
data: seriesData,
emphasis: { disabled: true },
barMaxWidth: barMaxWidth ?? BAR_WIDTHS.DEFAULT,
label: showLabel
@@ -81,7 +134,10 @@ const VerticalBar = ({
position: labelOptions?.position ?? "right",
color: labelOptions?.color,
distance: labelOptions?.distance,
formatter: (p: any) => (typeof p?.value === "number" ? fmt(p.value) : (p?.value ?? "")) as any,
formatter: (p: unknown) => {
const value = getActualValue(p);
return typeof value === "number" ? fmt(value) : value == null ? "" : String(value);
},
}
: undefined,
}

View File

@@ -169,10 +169,14 @@ return (
<BaseTableHeader title={title}/>
<div className="overflow-x-auto">
<table className={cn("kfpa-table kfpa-table", tableClassName)} style={{ minWidth: `${minWidth ?? minWidthPx}px` , maxWidth: maxWidth ? `${maxWidth}px` : undefined}}>
<table className={cn("kfpa-table kfpa-table", tableClassName)} style={{
minWidth: `${minWidth ?? minWidthPx}px`,
maxWidth: maxWidth ? `${maxWidth}px` : undefined
}}>
<colgroup>
{leadingColumnWidths.map((width, index) => (
<col key={`leading-col-${index}`} style={width ? { width, minWidth: width } : undefined} />
<col key={`leading-col-${index}`}
style={width ? {width, minWidth: width} : undefined}/>
))}
{columns.map((column, index) => {
const width = toCssSize(categoryColumnWidths?.[index] ?? column.width ?? categoryColumnWidth);
@@ -191,7 +195,8 @@ return (
className={cn(rowHeaderWidth ? undefined : "w-44", "border-none")}
style={{whiteSpace: "nowrap", ...rowHeaderStyle}}
/>
<td colSpan={columns.length} style={{ padding: 0, height: chartNode ? chartHeight : 0 }}>
<td colSpan={columns.length}
style={{padding: 0, height: chartNode ? chartHeight : 0}}>
{chartNode ? <div style={{width: "100%", height: "100%"}}>{chartNode}</div> : null}
</td>
</tr>
@@ -252,12 +257,16 @@ return (
const roundedValue = toRoundedNumber(rawValue, decimalPlaces);
if (roundedValue === null) {
return <td key={getColumnKey(column)} className={cn(column.cellClassName, row.cellClassName)} style={{ textAlign: column.align }}>-</td>;
return <td key={getColumnKey(column)}
className={cn(column.cellClassName, row.cellClassName, column.nullCellClassName)}
style={{textAlign: column.align}}>-</td>;
}
if (!signRow) {
return (
<td key={getColumnKey(column)} className={cn(column.cellClassName, row.cellClassName)} style={{ textAlign: column.align }}>
<td key={getColumnKey(column)}
className={cn(column.cellClassName, row.cellClassName)}
style={{textAlign: column.align}}>
{roundedValue.toFixed(decimalPlaces)}
</td>
);

View File

@@ -0,0 +1,9 @@
const CommentNote = () => {
return (
<p className="mt-3 content-text-base">
▶ : 완료&nbsp;&nbsp;/&nbsp;&nbsp;▷ : 진행 중
</p>
);
};
export default CommentNote;

View File

@@ -1,9 +1,24 @@
const CsiFormulaNote = () => {
return (
<>
<p className="mt-3 content-text-base">
※ 고객만족지수(CSI, Customer Satisfaction Index) = 고객 만족도조사 직접요소 항목 점수 X 가중치 + 고객
만족도조사 간접요소 항목 점수 X 가중치
</p>
<p className="mt-3 content-text-base">
※ 주요 고객 대상 : 안전점검(특수건물 관계자)
&nbsp;/&nbsp;&nbsp;UCIS(사원사 등)
&nbsp;/&nbsp;&nbsp;Bridge 플랫폼(사원사, 일반회원 등)
&nbsp;/&nbsp;&nbsp;방재컨설팅(발주처 관계자 약 20명)
&nbsp;/&nbsp;&nbsp;보험업무(보험 계약 담당자 약 300명)
&nbsp;/&nbsp;&nbsp;화재조사(사원사 손해사정부서 총 11명)
</p>
<p className="mt-3 content-text-base">
※ 응답 데이터 업데이트 주기 : 안전점검(매일 실시간)
&nbsp;/&nbsp;&nbsp;UCIS, Bridge플랫폼, 보험업무, 화재조사(매월 말)
&nbsp;/&nbsp;&nbsp;방재컨설팅(각 용역이 완료되는 하반기에 진행 예정)
</p>
</>
);
};

View File

@@ -2,7 +2,9 @@
import DataTable from "@/components/table/DataTable";
import type { DataColumn } from "@/components/table/types";
import { cn } from "@/lib/utils";
import type { CommentColumn, CommentField, CommentValue, DashboardCommentRowConfig } from "@/types/kfpa";
import CommentNote from "@/components/kfpa/CommentNote";
type CommentTableRow = DashboardCommentRowConfig & Record<string, unknown>;
@@ -63,12 +65,22 @@ const CustomerSatisfactionCommentTable = ({
const value = String(draft[column.key]?.[row.field] ?? "");
if (!isEditing) {
return <div className="min-h-24 whitespace-pre-wrap text-left">{value || "-"}</div>;
return (
<div className={cn(
"min-h-24 whitespace-pre-wrap text-left",
"leading-[1.5] content-text-lg"
)}>
{value || "-"}
</div>
);
}
return (
<textarea
className="min-h-28 w-full resize-y border border-gray-300 bg-background p-2 text-sm outline-none focus:border-primary"
className={cn(
"h-24 w-full resize-y border border-gray-300 bg-background p-2",
"leading-[1.5] content-text-lg outline-none focus:border-primary"
)}
value={value}
onChange={(event) => onChange(column.key, row.field, event.target.value)}
/>
@@ -78,6 +90,7 @@ const CustomerSatisfactionCommentTable = ({
];
return (
<>
<DataTable
columns={tableColumns}
rows={tableRows}
@@ -85,6 +98,8 @@ const CustomerSatisfactionCommentTable = ({
subheadRowClassName="bg-red-50"
wrapperClassName="w-full"
/>
<CommentNote/>
</>
);
};

View File

@@ -36,12 +36,14 @@ export type CustomerSatisfactionDetailProps = {
selectedDiv: string;
sectionTitleSuffix?: string;
viewSubTitle?: boolean;
widthClassName?: string;
};
const CustomerSatisfactionDetail = ({
selectedDiv,
sectionTitleSuffix,
viewSubTitle = true,
widthClassName = "w-full",
}: CustomerSatisfactionDetailProps) => {
const searchParams = useSearchParams();
const queryClient = useQueryClient();
@@ -122,7 +124,7 @@ const CustomerSatisfactionDetail = ({
}
return (
<div className="w-full">
<div className={widthClassName}>
<SectionTitle title={`${getSideMenuLabel(categoryKey, selectedDiv)} ${sectionTitleSuffix ?? '상세 내역'}`} />
<div className="mt-4 flex w-full items-start gap-16 overflow-x-auto pb-2">

View File

@@ -55,6 +55,13 @@ const CustomerSatisfactionSummary = () => {
: undefined,
align: "center",
}));
columns
.filter((column) => SUMMARY_CATEGORY_KEYS.includes(column.key ?? ""))
.forEach((column) => {
column.nullCellClassName = "bg-null text-null"
})
const categories = summaryColumns.map(getSummaryColumnLabel);
const rows: TopChartTableRow[] =
@@ -146,7 +153,7 @@ const CustomerSatisfactionSummary = () => {
signStyle={KFPA_GAP_SIGN_STYLE}
minWidth={tableLayout.tableWidth}
maxWidth={tableLayout.tableWidth}
chartHeight={180}
chartHeight={280}
chart={
<VerticalBar
data={chartData}
@@ -155,8 +162,9 @@ const CustomerSatisfactionSummary = () => {
valueFormatter={(value) => value.toFixed(KFPA_DECIMAL_POINT)}
barMaxWidth={30}
showFocusLabel="all"
labelOptions={{ position: "top", distance: 4 }}
grid={{ left: 0, right: 0, top: 20, bottom: 5 }}
labelOptions={{ position: "top", distance: 4, minPositionValue: 3.99 }}
legend={{top:50}}
grid={{ left: 0, right: 0, top: 120, bottom: 5 }}
xAxis={{
type: "category",
data: categories,
@@ -166,7 +174,7 @@ const CustomerSatisfactionSummary = () => {
}}
yAxis={{
type: "value",
min: 4,
min: 3.95,
max: 5,
axisLabel: { show: false },
axisTick: { show: false },

View File

@@ -225,8 +225,8 @@ const CustomerSatisfactionTotal = () => {
valueFormatter={(value) => value.toFixed(2)}
barMaxWidth={30}
showFocusLabel="all"
labelOptions={{ position: "top", distance: 4 }}
grid={{ left: 0, right: 0, top: 20, bottom: 5 }}
labelOptions={{ position: "top", distance: 4 , minPositionValue: 3.99}}
grid={{ left: 0, right: 0, top: 30, bottom: 5 }}
xAxis={{
type: "category",
data: categories,
@@ -236,7 +236,7 @@ const CustomerSatisfactionTotal = () => {
}}
yAxis={{
type: "value",
min: 4,
min: 3.95,
max: 5,
axisLabel: { show: false },
axisTick: { show: false },

View File

@@ -9,6 +9,7 @@ type TableColumnShared<T> = {
align?: TableColumnAlign;
headerClassName?: string;
cellClassName?: string;
nullCellClassName?: string;
render?: (row: T) => React.ReactNode;
};

View File

@@ -258,9 +258,9 @@ export const DASHBOARD_METRICS_BY_CATEGORY = {
} as const;
export const DASHBOARD_COMMENT_COLUMNS = [
{ key: "performance25", label: "25년 성과" },
{ key: "plan26", label: "26년 업무계획" },
{ key: "performance26", label: "26년 업무계획 진행률 및 성과" },
{ key: "performance25", label: "25년 고객 관점 주요 성과" },
//{ key: "plan26", label: "26년 업무계획" },
{ key: "performance26", label: "26년 고객 관점 주요 성과" },
] as const;
const DEFAULT_DASHBOARD_COMMENT_ROWS = [

View File

@@ -79,7 +79,6 @@ export const getAverageGapValue = (
key: string,
wave: number,
) => {
console.log(averageKey, key)
if(averageKey === key) return null;
const averageValue = roundNumber(getSummaryCsiValue(dataMap, averageKey, wave), KFPA_DECIMAL_POINT);
@@ -95,8 +94,7 @@ export const getSelectedDetail = (data: Record<string, DivDetailData> | undefine
};
export const getCommentColumns = (commentValues?: Record<string, CommentValue>): CommentColumn[] => {
const keys = Object.keys(commentValues ?? {});
const selectedKeys = keys.length > 0 ? keys : DASHBOARD_COMMENT_COLUMNS.map((column) => column.key);
const selectedKeys = DASHBOARD_COMMENT_COLUMNS.map((column) => column.key);
return selectedKeys.map((key, index) => ({
key,

111
src/proxy.ts Normal file
View File

@@ -0,0 +1,111 @@
import { NextRequest, NextResponse } from "next/server";
const IP_WHITELIST_ENV = "IP_WHITELIST";
const LOCAL_IPS = new Set(["127.0.0.1", "::1"]);
const normalizeIp = (ip: string) => {
const trimmed = ip.trim();
if (!trimmed) return "";
if (trimmed.startsWith("::ffff:")) return trimmed.slice("::ffff:".length);
const withoutBrackets = trimmed.replace(/^\[|\]$/g, "");
const portSeparatorIndex = withoutBrackets.lastIndexOf(":");
if (
portSeparatorIndex > -1 &&
withoutBrackets.indexOf(":") === portSeparatorIndex &&
/^\d+$/.test(withoutBrackets.slice(portSeparatorIndex + 1))
) {
return withoutBrackets.slice(0, portSeparatorIndex);
}
return withoutBrackets;
};
const getClientIp = (request: NextRequest) => {
const forwardedFor = request.headers.get("x-forwarded-for");
if (forwardedFor) {
return normalizeIp(forwardedFor.split(",")[0]);
}
return normalizeIp(
request.headers.get("x-real-ip") ??
request.headers.get("cf-connecting-ip") ??
request.headers.get("true-client-ip") ??
""
);
};
const ipv4ToNumber = (ip: string) => {
const parts = ip.split(".");
if (parts.length !== 4) return null;
return parts.reduce<number | null>((acc, part) => {
if (acc === null || !/^\d+$/.test(part)) return null;
const value = Number(part);
if (value < 0 || value > 255) return null;
return ((acc << 8) + value) >>> 0;
}, 0);
};
const isIpv4InCidr = (ip: string, cidr: string) => {
const [rangeIp, prefixRaw] = cidr.split("/");
const prefix = Number(prefixRaw);
const target = ipv4ToNumber(ip);
const range = ipv4ToNumber(rangeIp);
if (target === null || range === null || !Number.isInteger(prefix) || prefix < 0 || prefix > 32) {
return false;
}
const mask = prefix === 0 ? 0 : (0xffffffff << (32 - prefix)) >>> 0;
return (target & mask) === (range & mask);
};
const parseWhitelist = () =>
(process.env[IP_WHITELIST_ENV] ?? "")
.split(",")
.map((ip) => normalizeIp(ip))
.filter(Boolean);
const isAllowedIp = (clientIp: string) => {
const whitelist = parseWhitelist();
if (whitelist.length === 0) {
return process.env.ENV === "local" && LOCAL_IPS.has(clientIp);
}
return whitelist.some((allowedIp) => {
if (allowedIp.includes("/")) {
return isIpv4InCidr(clientIp, allowedIp);
}
return clientIp === allowedIp;
});
};
export function proxy(request: NextRequest) {
const pathname = request.nextUrl.pathname;
if (pathname === "/403") {
return NextResponse.next();
}
const clientIp = getClientIp(request);
if (clientIp && isAllowedIp(clientIp)) {
return NextResponse.next();
}
const url = request.nextUrl.clone();
url.pathname = "/403";
url.search = "";
return NextResponse.redirect(url);
}
export const config = {
matcher: ["/((?!api|_next/static|_next/image|favicon.ico|.*\\..*).*)"],
};