fix(numbering): correct error state handling in MetricsDashboard
CI / CD Pipeline / build (push) Successful in 5m33s
CI / CD Pipeline / deploy (push) Successful in 7m34s

- Change state type to allow undefined distinction from empty object
- Set undefined on error instead of empty object
- Fixes test failure where 'No metrics available' was not displayed
This commit is contained in:
2026-06-14 07:03:10 +07:00
parent 7e8f4859cd
commit 56f9544cb0
@@ -7,7 +7,7 @@ import { documentNumberingService } from '@/lib/services/document-numbering.serv
import { NumberingMetrics } from '@/types/dto/numbering.dto'; import { NumberingMetrics } from '@/types/dto/numbering.dto';
export function MetricsDashboard() { export function MetricsDashboard() {
const [metrics, setMetrics] = useState<Partial<NumberingMetrics>>({}); const [metrics, setMetrics] = useState<Partial<NumberingMetrics> | undefined>(undefined);
const [loading, setLoading] = useState(true); const [loading, setLoading] = useState(true);
useEffect(() => { useEffect(() => {
@@ -16,7 +16,7 @@ export function MetricsDashboard() {
const data = await documentNumberingService.getMetrics(); const data = await documentNumberingService.getMetrics();
setMetrics(data); setMetrics(data);
} catch (_error) { } catch (_error) {
setMetrics({}); setMetrics(undefined);
} finally { } finally {
setLoading(false); setLoading(false);
} }