[meilingrl]

What changed

Type

• feat — new feature
• fix — bug fix
• refactor — no behavior change
• docs / task — documentation or task lifecycle only
• chore — tooling, config, deps

Testing

• cd backend && mvnw.cmd test — all pass
• cd frontend && npm test — all pass
• cd frontend && npm run build — no errors
• Manual smoke: golden path works, no obvious regressions

Checklist

• CHANGELOG.md prepended (skip for docs-only)
• API spec updated if endpoint contract changed (docs/09-api-spec/)
• .http smoke file updated if endpoint added or changed (docs/06-http/)
• Task doc archived if this closes an active task (docs/08-tasks/)
• No unrelated files staged

Notes

[gemini-code-assist]

Code Review

This pull request optimizes code structure and CSS reuse by extracting scoped styles from Vue SFCs into adjacent CSS files, introducing reusable UI utility classes, and refactoring AdminServiceImpl to delegate dashboard and CSV export generation to dedicated builder classes (AdminDashboardBuilder and AdminCsvExportBuilder). The review feedback highlights critical runtime issues in the new builders, specifically potential NullPointerException failures when using List.of(...) with nullable database fields in the CSV export methods, and recommends enhancing asLocalDateTime to support Timestamp and Date types to ensure robust date parsing across different database drivers.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

Using List.of(...) here will throw a NullPointerException at runtime if any of the mapped database values (such as nickname, verificationStatus, privilegeLabel, creditLevel, or lastLoginAt) are null. Since database rows often contain nullable columns, it is safer to use java.util.Arrays.asList(...) which permits null elements. The downstream CSV builder already handles null values gracefully.

Suggested change

	rows.stream().map(this::sanitizeAdminUser).map(row -> List.of(
	row.get("id"),
	row.get("username"),
	row.get("nickname"),
	row.get("status"),
	row.get("role"),
	row.get("verificationStatus"),
	row.get("privilegeLabel"),
	row.get("creditLevel"),
	row.get("isRestricted"),
	row.get("registeredAt"),
	row.get("lastLoginAt")
	)).toList()
	rows.stream().map(this::sanitizeAdminUser).map(row -> java.util.Arrays.asList(
	row.get("id"),
	row.get("username"),
	row.get("nickname"),
	row.get("status"),
	row.get("role"),
	row.get("verificationStatus"),
	row.get("privilegeLabel"),
	row.get("creditLevel"),
	row.get("isRestricted"),
	row.get("registeredAt"),
	row.get("lastLoginAt")
	)).toList()

[gemini-code-assist]

Using List.of(...) here will throw a NullPointerException at runtime if any of the mapped database values (such as categoryName, sellerName, shopId, shopName, reviewStatus, favoriteCount, or updatedAt) are null. Using java.util.Arrays.asList(...) is safer as it permits null elements, which are already handled gracefully by the downstream CSV builder.

Suggested change

	rows.stream().map(row -> List.of(
	row.get("id"),
	row.get("title"),
	row.get("categoryName"),
	row.get("sellerUserId"),
	row.get("sellerName"),
	row.get("shopId"),
	row.get("shopName"),
	row.get("productType"),
	row.get("status"),
	row.get("reviewStatus"),
	row.get("price"),
	row.get("stock"),
	row.get("viewCount"),
	row.get("favoriteCount"),
	row.get("createdAt"),
	row.get("updatedAt")
	)).toList()
	rows.stream().map(row -> java.util.Arrays.asList(
	row.get("id"),
	row.get("title"),
	row.get("categoryName"),
	row.get("sellerUserId"),
	row.get("sellerName"),
	row.get("shopId"),
	row.get("shopName"),
	row.get("productType"),
	row.get("status"),
	row.get("reviewStatus"),
	row.get("price"),
	row.get("stock"),
	row.get("viewCount"),
	row.get("favoriteCount"),
	row.get("createdAt"),
	row.get("updatedAt")
	)).toList()

[gemini-code-assist]

The current implementation of asLocalDateTime only handles instances of LocalDateTime. Depending on the database driver and configuration, date/time fields retrieved from the database (such as submittedAt) might be returned as java.sql.Timestamp or java.util.Date. If so, this method will return null, causing date-based calculations on the dashboard to silently fail or return zero values. Supporting these types explicitly makes the method much more robust.

    private LocalDateTime asLocalDateTime(Object value) {
        if (value instanceof LocalDateTime localDateTime) {
            return localDateTime;
        }
        if (value instanceof java.sql.Timestamp timestamp) {
            return timestamp.toLocalDateTime();
        }
        if (value instanceof java.util.Date date) {
            return date.toInstant().atZone(java.time.ZoneId.systemDefault()).toLocalDateTime();
        }
        return null;
    }