From e1968dcdc5e51073d809f52bfe3a2dd105aebee5 Mon Sep 17 00:00:00 2001 From: QuantCode Agent Date: Mon, 28 Sep 2026 08:35:14 +0000 Subject: [PATCH] fix: resolve cross-package test failures and type errors - utils: formatDate emits en-AU D/MM/YYYY without leading-zero day - ui: Button renders aria-label, with fallback for icon-only buttons - ui: DataTable sort toggle uses functional state update (stale closure) - web: import renamed useDebounce instead of useThrottle - config: root bunfig preloads DOM setup; tsconfig loads bun-types --- apps/web/src/lib/api.ts | 13 +++------- bunfig.toml | 2 +- packages/ui/src/components/Button/Button.tsx | 23 +++++++++------- .../ui/src/components/DataTable/DataTable.tsx | 11 +------- packages/utils/src/format/date.ts | 26 +++++++++---------- tsconfig.json | 1 + 6 files changed, 33 insertions(+), 43 deletions(-) diff --git a/apps/web/src/lib/api.ts b/apps/web/src/lib/api.ts index 2d4731b..56c1c04 100644 --- a/apps/web/src/lib/api.ts +++ b/apps/web/src/lib/api.ts @@ -1,15 +1,8 @@ /** * API client utilities for the web app. - * - * BUG: imports `useThrottle` from @e2e/utils, but that hook was renamed to - * `useDebounce`. This causes a TypeScript error and a runtime crash. - * - * Fix: change the import to `useDebounce`. */ -// BUG: useThrottle no longer exists — was renamed to useDebounce -import { useThrottle } from "@e2e/utils" -import { formatDate, formatAUD } from "@e2e/utils" +import { useDebounce, formatDate, formatAUD } from "@e2e/utils" export const BASE_URL = process.env.API_URL ?? "http://localhost:3000" @@ -28,5 +21,5 @@ export async function fetchPosts() { // Re-export formatting utilities used throughout the app export { formatDate, formatAUD } -// Re-export the debounce hook (currently broken import) -export { useThrottle as useSearchDebounce } +// Re-export the debounce hook under the app-facing name +export { useDebounce as useSearchDebounce } diff --git a/bunfig.toml b/bunfig.toml index 3258d71..1cb73b3 100644 --- a/bunfig.toml +++ b/bunfig.toml @@ -1,2 +1,2 @@ [test] -environment = "happy-dom" \ No newline at end of file +preload = ["./packages/ui/test/setup.ts"] \ No newline at end of file diff --git a/packages/ui/src/components/Button/Button.tsx b/packages/ui/src/components/Button/Button.tsx index af65c97..051ae9a 100644 --- a/packages/ui/src/components/Button/Button.tsx +++ b/packages/ui/src/components/Button/Button.tsx @@ -17,13 +17,11 @@ type Props = { /** * Button component. * - * BUG: When `iconOnly` is true, the button renders without visible text. - * An `aria-label` is required for screen reader accessibility (WCAG 2.1 SC 4.1.2), - * but the component does not enforce or warn about its absence. - * - * The test in Button.test.tsx checks that an icon-only button has an accessible name. - * Fix: throw/warn in development when `iconOnly && !aria-label`, or always render - * the aria-label attribute when iconOnly is true. + * Icon-only buttons render no visible text, so they must expose an accessible + * name via `aria-label` to satisfy WCAG 2.2 SC 4.1.2 (Name, Role, Value). + * When `iconOnly` is set without an explicit label we fall back to a generic + * name and warn in development, so the omission surfaces during authoring + * rather than shipping a control screen readers announce only as "button". */ export function Button({ children, @@ -34,13 +32,20 @@ export function Button({ onClick, "aria-label": ariaLabel, }: Props) { + if (iconOnly && !ariaLabel && process.env.NODE_ENV !== "production") { + console.warn( + "Button: `iconOnly` requires an `aria-label` to provide an accessible name (WCAG 2.2 SC 4.1.2).", + ) + } + + const accessibleName = iconOnly ? (ariaLabel ?? "Button") : ariaLabel + return (