fix(types): fix normalizeAbsent.test.tsx type errors

[jdhoffa]

• Add undefined to union types in MockObject type definition
• Add array bounds check in normalizeList test
• Remove unnecessary @ts-expect-error directive

Relates to #514

[github-actions]

Expected version change and release notes:

1.5.0-dev.19 (v1.5.0-dev.18...fix-ts_errors_normalize_absent ) (2025-11-05T13:53 UTC)

Fixes

• types: fix normalizeAbsent.test.tsx type errors (f53589d)

[Copilot]

Pull Request Overview

This PR updates the normalizeAbsent test suite to improve TypeScript type safety and add runtime array validation. The changes include explicit undefined in union types for optional fields, removal of a ts-expect-error suppression, and addition of a runtime check for array bounds.

• Explicitly added | undefined to optional field type definitions in MockObject
• Removed @ts-expect-error comment that was suppressing type errors for non-normalized fields
• Added runtime validation to ensure array has expected elements before accessing them

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

[nitpick] Adding | undefined to optional properties is redundant in TypeScript. The ? operator already includes undefined in the type union. For consistency and conciseness, consider removing the explicit | undefined from all optional property declarations (lines 7-13).

Suggested change

	temperature?: string | null | undefined;
	targetYear?: number | null | undefined;
	targetType?: "absolute" | "intensity" | null | undefined;
	abool?: boolean | null | undefined;
	zero?: number | null | undefined;
	empty?: string | null | undefined;
	missing?: string | undefined;
	temperature?: string | null;
	targetYear?: number | null;
	targetType?: "absolute" | "intensity" | null;
	abool?: boolean | null;
	zero?: number | null;
	empty?: string | null;
	missing?: string;

[Copilot]

The runtime check uses truthiness evaluation (!out[0]) which would fail if the array element exists but has a falsy value (e.g., an object with only falsy properties). Consider using out.length !== 3 instead to check only the array length: if (out.length !== 3) throw new Error('Expected array to have 3 items');

Suggested change

	if (!out[0] || !out[1] || !out[2])
	if (out.length !== 3)

[github-actions]

Azure Static Web Apps: Your stage site is ready! Visit it here: https://proud-glacier-0f640931e-520.westus2.2.azurestaticapps.net

[AlexAxthelm]

Noting that for other tests, I would probably cast MockObject as an actual type, but in this case, since we're testing a generic util, looks good.