@automattic/charts 3.2.0 → 4.0.0

package/src/providers/chart-context/private/theme-override-vars.ts

@@ -1,131 +0,0 @@
-import { SERIES_SLOT_COUNT, seriesRole } from './series-palette';
-import type { ChartTheme } from '../../../types';
-
-/*
- * `process.env.NODE_ENV` is replaced by the bundler at build time. Declare a
- * minimal `process` locally so this file type-checks as source under `jetpack:src`.
- */
-declare const process: { env: Record< string, string | undefined > };
-
-// The consumer theme fields that correspond to an emitted catalog role, and the role each one overrides. Each role must be read by exactly the elements its field controlled before the role existed: `svgLabelSmall.fill` maps to the narrow `--a8c-charts-color-label-axis` rather than `--a8c-charts-color-label`, because the broad role is also read by legend labels, heatmap cell values, funnel labels and the line-chart tooltip, which that field never moved.
-//
-// `theme.colors` is the one field mapped by position rather than by name: entry N publishes slot N+1, which is what makes it sugar over the five slots rather than a second palette with its own precedence.
-const ROLE_FOR_FIELD: Array< [ string, ( theme: Partial< ChartTheme > ) => string | undefined ] > =
-	[
-		[ '--a8c-charts-color-background', theme => theme.backgroundColor ],
-		[ '--a8c-charts-color-grid', theme => theme.gridStyles?.stroke ],
-		[ '--a8c-charts-color-axis', theme => theme.xAxisLineStyles?.stroke ],
-		[ '--a8c-charts-color-tick', theme => theme.xTickLineStyles?.stroke ],
-		[ '--a8c-charts-color-label-axis', theme => theme.svgLabelSmall?.fill ],
-		[ '--a8c-charts-color-label-background', theme => theme.labelBackgroundColor ],
-		[ '--a8c-charts-color-label-on-fill', theme => theme.labelTextColor ],
-		...Array.from(
-			{ length: SERIES_SLOT_COUNT },
-			( _, index ): [ string, ( theme: Partial< ChartTheme > ) => string | undefined ] => [
-				seriesRole( index + 1 ),
-				theme => theme.colors?.[ index ],
-			]
-		),
-	];
-
-let warnedAboutExtraColors = false;
-
-/**
- * Warns once when a consumer passes more colors than there are slots to publish them into.
- *
- * @param count - How many entries `theme.colors` holds.
- */
-function warnOnceAboutExtraColors( count: number ): void {
-	if ( warnedAboutExtraColors || process.env.NODE_ENV === 'production' ) {
-		return;
-	}
-
-	warnedAboutExtraColors = true;
-	// eslint-disable-next-line no-console
-	console.warn(
-		`[Charts] theme.colors holds ${ count } colors and the palette has ${ SERIES_SLOT_COUNT } slots, so entries past the ${ SERIES_SLOT_COUNT }th are ignored. ` +
-			'Set a per-series color with `options.stroke` instead.'
-	);
-}
-
-/**
- * The variable a `theme` prop override is published as, one layer outside the role itself.
- *
- * `chart-scope.scss` declares each of these roles as `var(<role>-theme, <catalog default>)`, so an override that is invalid at computed-value time — a fallback-less `var()` naming a token the host never set — only invalidates this variable, and the role still resolves its mapped `--wpds-*` token. Published as the role directly, such a value took the role and every bare `var(<role>)` read site down with it.
- *
- * @param role - The catalog role being overridden.
- * @return The custom property carrying the consumer's value.
- */
-export const themeLayerVar = ( role: string ): string => `${ role }-theme`;
-
-/** Every role whose catalog entry must read a theme layer. `src/styles/test/chart-scope.test.ts` checks the stylesheet against this. */
-export const THEME_LAYERED_ROLES: readonly string[] = ROLE_FOR_FIELD.map( ( [ role ] ) => role );
-
-/**
- * Whether a value reads the role it is being published for, which would make the catalog entry depend on itself.
- *
- * The dependency runs `<role>: var(<role>-theme, …)`, so a value naming `<role>` closes a cycle through the catalog entry. CSS marks every custom property in a cycle invalid at computed-value time — the role's own fallback is *not* used, so the token resolves to nothing and every chart loses that color. Verified in Chrome: `--role-theme: var(--role, blue); --role: var(--role-theme, green)` leaves `--role` empty, not `green`.
- *
- * Three things this has to get right, none of which a plain substring test gets:
- *
- * `var()` permits whitespace after the opening paren, so testing for `var(<role>` misses `var( --a8c-charts-color-grid, … )`.
- *
- * Several roles are prefixes of others (`--a8c-charts-color-label` of `--a8c-charts-color-label-secondary`), and every role is a prefix of its own theme layer. A prefix match would read a legitimate cross-role pointer as a self-reference and silently drop the override, so the role must be followed by something that cannot continue an identifier — `-` included. A value naming `<role>-theme` is therefore not treated as a self-reference: that cycle is confined to the theme layer, which leaves the role free to fall back to the catalog default.
- *
- * `resolveCssVariable` also accepts a bare custom-property name with no `var()` wrapper (`--a8c-charts-color-grid`), so that is legal `theme` input too. It forms no cycle — custom properties accept arbitrary token streams — so it survives as a literal string and drops silently at the use site instead of falling back to the catalog default.
- *
- * @param value - The consumer's value for the field.
- * @param role  - The catalog role this value would override.
- * @return True when the value reads `role`, so it must not be published.
- */
-const readsOwnRole = ( value: string, role: string ): boolean =>
-	value.trim() === role ||
-	new RegExp( `var\\(\\s*${ role.replace( /[.*+?^${}()|[\]\\]/g, '\\$&' ) }(?![\\w-])` ).test(
-		value
-	);
-
-export type ThemeOverrides = {
-	/** The custom properties to write on the provider wrapper. */
-	vars: Record< string, string >;
-	/** Every mapped role the consumer set a value for, whether or not it was published. */
-	roles: readonly string[];
-};
-
-/**
- * Maps a sparse consumer theme onto the theme-layer variables its overridden catalog roles read, so CSS-painted and JS-resolved colors read one source.
- *
- * A value that reads the role it would override is left unpublished — that is the default theme's own pointer surviving `mergeThemes`, and publishing it would invalidate the role. The role is still reported in `roles`: `withCatalogPointers` restores its theme field to the catalog pointer either way, so CSS and visx agree on the catalog default rather than visx painting a literal CSS never sees.
- *
- * `theme.colors` publishes through the same mechanism, one slot per entry, so a CSS declaration of `--a8c-charts-color-series-N` still beats it and a short array leaves the later slots unset rather than blank.
- *
- * @param theme - The consumer's `theme` prop, before merging with the default theme.
- * @return The wrapper's custom properties, and the roles the consumer overrode.
- */
-export const themeOverrideVars = ( theme?: Partial< ChartTheme > ): ThemeOverrides => {
-	if ( ! theme ) {
-		return { vars: {}, roles: [] };
-	}
-
-	if ( Array.isArray( theme.colors ) && theme.colors.length > SERIES_SLOT_COUNT ) {
-		warnOnceAboutExtraColors( theme.colors.length );
-	}
-
-	const vars: Record< string, string > = {};
-	const roles: string[] = [];
-
-	for ( const [ role, read ] of ROLE_FOR_FIELD ) {
-		const value = read( theme );
-
-		if ( typeof value !== 'string' || value === '' ) {
-			continue;
-		}
-
-		roles.push( role );
-
-		if ( ! readsOwnRole( value, role ) ) {
-			vars[ themeLayerVar( role ) ] = value;
-		}
-	}
-
-	return { vars, roles };
-};

package/src/providers/chart-context/private/with-catalog-pointers.ts

@@ -1,93 +0,0 @@
-import { defaultTheme } from '../themes';
-import { SERIES_PALETTE_POINTERS, SERIES_SLOT_COUNT, seriesRole } from './series-palette';
-import type { CompleteChartTheme } from '../../../types';
-
-/**
- * The pointer one palette slot is restored to.
- *
- * Unlike the other roles, this keeps the consumer's own color as the pointer's terminal literal instead of the catalog's. The literal is only ever reached where `getComputedStyle` resolves nothing — SSR and jsdom — and there the palette is the one field where falling back to the catalog default would be visible: every series would paint the same seeded blue. In a browser the slot resolves first, so a CSS declaration of it still outranks the consumer's `theme.colors`.
- *
- * @param index - The slot's zero-based index in `colors`.
- * @param value - The merged theme's entry for it.
- * @return The catalog pointer for that slot.
- */
-const seriesPointer = ( index: number, value: string | undefined ): string => {
-	const role = seriesRole( index + 1 );
-
-	// Idempotent: `withCatalogPointers` runs this once per overridden slot, so from the second call on the array already holds pointers.
-	if ( typeof value === 'string' && value.startsWith( `var(${ role }` ) ) {
-		return value;
-	}
-
-	// A slot the consumer left empty keeps the catalog's own pointer, so a CSS declaration of it still reaches the palette.
-	if ( typeof value !== 'string' || value === '' ) {
-		return SERIES_PALETTE_POINTERS[ index ];
-	}
-
-	return `var(${ role }, ${ value })`;
-};
-
-// Restores each overridden role's mapped theme field to the catalog pointer already written for it — `defaultTheme` for the ordinary roles, `series-palette.ts` for the palette slots — so the value comes from the one place that declares it rather than a second, hand-copied literal.
-//
-// Every series slot restores the whole `colors` array, not just its own entry. `mergeThemes` replaces arrays outright, so a consumer passing two colors would otherwise leave a two-entry palette and put slots 3 to 5 out of reach of a CSS declaration that sets them.
-const CATALOG_RESTORE_FOR_ROLE: Record<
-	string,
-	( theme: CompleteChartTheme ) => Partial< CompleteChartTheme >
-> = {
-	// Each of the five entries rebuilds the whole array, so a consumer overriding every slot runs this five times. That is deliberate rather than merely tolerated: `seriesPointer` is idempotent, so every pass after the first is a no-op, and five allocations of a five-element array is not worth a special case in a map that is otherwise one entry per role.
-	...Object.fromEntries(
-		Array.from( { length: SERIES_SLOT_COUNT }, ( _, index ) => [
-			seriesRole( index + 1 ),
-			( theme: CompleteChartTheme ) => ( {
-				colors: SERIES_PALETTE_POINTERS.map( ( _pointer, slot ) =>
-					seriesPointer( slot, theme.colors?.[ slot ] )
-				),
-			} ),
-		] )
-	),
-	'--a8c-charts-color-background': () => ( { backgroundColor: defaultTheme.backgroundColor } ),
-	'--a8c-charts-color-grid': theme => ( {
-		gridStyles: { ...theme.gridStyles, stroke: defaultTheme.gridStyles.stroke },
-	} ),
-	'--a8c-charts-color-axis': theme => ( {
-		xAxisLineStyles: { ...theme.xAxisLineStyles, stroke: defaultTheme.xAxisLineStyles.stroke },
-	} ),
-	'--a8c-charts-color-tick': theme => ( {
-		xTickLineStyles: { ...theme.xTickLineStyles, stroke: defaultTheme.xTickLineStyles.stroke },
-	} ),
-	'--a8c-charts-color-label-axis': theme => ( {
-		svgLabelSmall: { ...theme.svgLabelSmall, fill: defaultTheme.svgLabelSmall.fill },
-	} ),
-	'--a8c-charts-color-label-background': () => ( {
-		labelBackgroundColor: defaultTheme.labelBackgroundColor,
-	} ),
-	'--a8c-charts-color-label-on-fill': () => ( { labelTextColor: defaultTheme.labelTextColor } ),
-};
-
-/**
- * Restores the mapped theme fields of `overriddenRoles` to their catalog pointer, so the theme-layer variable `themeOverrideVars` writes on the provider wrapper is the only carrier for an overridden role — CSS and the JS bridge (`useXYChartTheme`) then resolve it through the same cascade instead of visx reading a baked literal that can disagree with a closer CSS override.
- *
- * This covers roles `themeOverrideVars` deliberately left unpublished as well as the ones it published. A value that reads its own role is not publishable, but leaving visx the consumer's literal is what the whole mechanism exists to prevent: `theme={ { gridStyles: { stroke: 'var(--brand, var(--a8c-charts-color-grid, red))' } } }` would have CSS paint the catalog default while visx painted `--brand`.
- *
- * Every field outside the mapped roles is left exactly as `merged` provided it: those aren't published as theme-layer vars, so rewriting them would erase a consumer's override with no replacement carrier.
- *
- * @param merged          - The consumer theme merged onto `defaultTheme` (`mergeThemes` output).
- * @param overriddenRoles - The catalog roles the consumer overrode, from `themeOverrideVars`.
- * @return A new theme object; `merged` is not mutated.
- */
-export const withCatalogPointers = (
-	merged: CompleteChartTheme,
-	overriddenRoles: readonly string[]
-): CompleteChartTheme => {
-	let result = merged;
-
-	for ( const role of overriddenRoles ) {
-		const restore = CATALOG_RESTORE_FOR_ROLE[ role ];
-
-		if ( restore ) {
-			result = { ...result, ...restore( result ) };
-		}
-	}
-
-	return result;
-};

package/src/providers/chart-context/test/theme-override-vars-guard.test.tsx

@@ -1,29 +0,0 @@
-import { render, screen } from '@testing-library/react';
-import { GlobalChartsProvider } from '../global-charts-provider';
-
-// The stock defaultTheme's mapped fields are themselves self-referential pointers (e.g. `gridStyles.stroke: 'var(--a8c-charts-color-grid, #dbdbdb)'`), so themeOverrideVars' own self-reference guard already filters them out no matter which theme object the provider passes in. That makes "reads theme, not providerTheme" unfalsifiable against the real default theme. Mocking the default here to a plain, non-pointer value removes that overlap, so this test only passes when the provider reads the raw consumer `theme` prop rather than the merged `providerTheme`.
-jest.mock( '../themes', () => {
-	const actual = jest.requireActual( '../themes' );
-	return {
-		...actual,
-		defaultTheme: {
-			...actual.defaultTheme,
-			gridStyles: { ...actual.defaultTheme.gridStyles, stroke: '#dbdbdb' },
-		},
-	};
-} );
-
-describe( 'GlobalChartsProvider wrapper style (discriminating guard test)', () => {
-	it( 'does not emit an instance override for a role the consumer left unset, even though the merged theme carries a concrete default value', () => {
-		render(
-			<GlobalChartsProvider theme={ { tickLength: 8 } }>
-				<div>child</div>
-			</GlobalChartsProvider>
-		);
-
-		const wrapper = screen.getByTestId( 'charts-scope' );
-
-		expect( wrapper.style.getPropertyValue( '--a8c-charts-color-grid-theme' ) ).toBe( '' );
-		expect( wrapper.style.getPropertyValue( '--a8c-charts-color-grid' ) ).toBe( '' );
-	} );
-} );

package/src/providers/chart-context/test/theme-override-vars.test.ts

@@ -1,183 +0,0 @@
-import {
-	THEME_LAYERED_ROLES,
-	themeLayerVar,
-	themeOverrideVars,
-} from '../private/theme-override-vars';
-
-describe( 'themeOverrideVars', () => {
-	it( 'returns nothing for an absent theme', () => {
-		expect( themeOverrideVars( undefined ) ).toEqual( { vars: {}, roles: [] } );
-	} );
-
-	it( 'returns nothing for a theme that overrides no mapped role', () => {
-		expect( themeOverrideVars( { tickLength: 8 } ) ).toEqual( { vars: {}, roles: [] } );
-	} );
-
-	// The value is published one layer outside the role — `chart-scope.scss` declares the role as `var(<role>-theme, <catalog default>)`. Published as the role itself, a value that is invalid at computed-value time (`var(--wpds-token)` with the token unset) would make the role invalid too, and every bare `var(--a8c-charts-color-grid)` read site would paint `unset` instead of falling back to the catalog default.
-	it( 'maps a grid stroke override onto the grid role’s theme layer', () => {
-		expect( themeOverrideVars( { gridStyles: { stroke: 'red' } } ) ).toEqual( {
-			vars: { '--a8c-charts-color-grid-theme': 'red' },
-			roles: [ '--a8c-charts-color-grid' ],
-		} );
-	} );
-
-	it( 'maps every supported role at once', () => {
-		expect(
-			themeOverrideVars( {
-				backgroundColor: '#111',
-				gridStyles: { stroke: '#222' },
-				xAxisLineStyles: { stroke: '#333' },
-				xTickLineStyles: { stroke: '#444' },
-				svgLabelSmall: { fill: '#555' },
-				labelBackgroundColor: '#556',
-				labelTextColor: '#557',
-				colors: [ '#661', '#662', '#663', '#664', '#665' ],
-			} )
-		).toEqual( {
-			vars: {
-				'--a8c-charts-color-background-theme': '#111',
-				'--a8c-charts-color-grid-theme': '#222',
-				'--a8c-charts-color-axis-theme': '#333',
-				'--a8c-charts-color-tick-theme': '#444',
-				'--a8c-charts-color-label-axis-theme': '#555',
-				'--a8c-charts-color-label-background-theme': '#556',
-				'--a8c-charts-color-label-on-fill-theme': '#557',
-				'--a8c-charts-color-series-1-theme': '#661',
-				'--a8c-charts-color-series-2-theme': '#662',
-				'--a8c-charts-color-series-3-theme': '#663',
-				'--a8c-charts-color-series-4-theme': '#664',
-				'--a8c-charts-color-series-5-theme': '#665',
-			},
-			roles: [
-				'--a8c-charts-color-background',
-				'--a8c-charts-color-grid',
-				'--a8c-charts-color-axis',
-				'--a8c-charts-color-tick',
-				'--a8c-charts-color-label-axis',
-				'--a8c-charts-color-label-background',
-				'--a8c-charts-color-label-on-fill',
-				'--a8c-charts-color-series-1',
-				'--a8c-charts-color-series-2',
-				'--a8c-charts-color-series-3',
-				'--a8c-charts-color-series-4',
-				'--a8c-charts-color-series-5',
-			],
-		} );
-	} );
-
-	it( 'publishes only theme-layer variables, never a catalog role directly', () => {
-		const { vars } = themeOverrideVars( {
-			backgroundColor: '#111',
-			gridStyles: { stroke: '#222' },
-			xAxisLineStyles: { stroke: '#333' },
-			xTickLineStyles: { stroke: '#444' },
-			svgLabelSmall: { fill: '#555' },
-			labelBackgroundColor: '#556',
-			labelTextColor: '#557',
-			colors: [ '#661', '#662', '#663', '#664', '#665' ],
-		} );
-
-		expect( Object.keys( vars ) ).toEqual( THEME_LAYERED_ROLES.map( themeLayerVar ) );
-	} );
-
-	// The narrow role is the whole point: the broad `--a8c-charts-color-label` is also read by legend labels, heatmap cell values, funnel labels and the line-chart tooltip, none of which `svgLabelSmall.fill` moved before the role was published as a custom property.
-	it( 'publishes an svg label override as the narrow axis-label role, not the broad one', () => {
-		expect( themeOverrideVars( { svgLabelSmall: { fill: 'red' } } ) ).toEqual( {
-			vars: { '--a8c-charts-color-label-axis-theme': 'red' },
-			roles: [ '--a8c-charts-color-label-axis' ],
-		} );
-	} );
-
-	// A short array is not padded: the later slots stay unset, so the palette compacts rather than repeating a color the consumer never chose.
-	it( 'publishes one palette slot per color and leaves the rest unset', () => {
-		expect( themeOverrideVars( { colors: [ 'red', 'blue' ] } ) ).toEqual( {
-			vars: {
-				'--a8c-charts-color-series-1-theme': 'red',
-				'--a8c-charts-color-series-2-theme': 'blue',
-			},
-			roles: [ '--a8c-charts-color-series-1', '--a8c-charts-color-series-2' ],
-		} );
-	} );
-
-	it( 'drops palette entries past the last slot', () => {
-		// Spied rather than asserted on: an over-long palette warns, and `@wordpress/jest-console` fails any test that leaves a console call unclaimed. The warning itself is covered below.
-		const warn = jest.spyOn( console, 'warn' ).mockImplementation( () => {} );
-		const { vars } = themeOverrideVars( {
-			colors: [ 'a', 'b', 'c', 'd', 'e', 'f', 'g' ],
-		} );
-
-		expect( vars[ '--a8c-charts-color-series-5-theme' ] ).toBe( 'e' );
-		expect( vars[ '--a8c-charts-color-series-6-theme' ] ).toBeUndefined();
-
-		warn.mockRestore();
-	} );
-
-	// Isolated so the warning's module-level latch starts unset — the assertion is that it warns once per module instance, not once per call.
-	it( 'warns once about the dropped entries, not once per render', () => {
-		jest.isolateModules( () => {
-			const warn = jest.spyOn( console, 'warn' ).mockImplementation( () => {} );
-			const {
-				themeOverrideVars: freshThemeOverrideVars,
-				// eslint-disable-next-line @typescript-eslint/no-require-imports -- isolateModules needs a synchronous require to get a module instance whose latch is unset.
-			} = require( '../private/theme-override-vars' ) as {
-				themeOverrideVars: typeof themeOverrideVars;
-			};
-
-			freshThemeOverrideVars( { colors: [ 'a', 'b', 'c', 'd', 'e', 'f' ] } );
-			freshThemeOverrideVars( { colors: [ 'a', 'b', 'c', 'd', 'e', 'f' ] } );
-
-			expect( warn ).toHaveBeenCalledTimes( 1 );
-			expect( warn ).toHaveBeenCalledWith( expect.stringContaining( 'holds 6 colors' ) );
-
-			warn.mockRestore();
-		} );
-	} );
-
-	it( 'ignores a value that is itself a pointer at the role it would override', () => {
-		expect(
-			themeOverrideVars( { gridStyles: { stroke: 'var(--a8c-charts-color-grid, #dbdbdb)' } } ).vars
-		).toEqual( {} );
-	} );
-
-	// A skipped value still reports its role, so `withCatalogPointers` restores the theme field. Without that, CSS would paint the catalog default while visx painted the consumer's literal — the divergence this whole mechanism exists to remove.
-	it( 'still reports the role of a value it refuses to publish', () => {
-		expect(
-			themeOverrideVars( {
-				gridStyles: { stroke: 'var(--brand, var(--a8c-charts-color-grid, red))' },
-			} )
-		).toEqual( { vars: {}, roles: [ '--a8c-charts-color-grid' ] } );
-	} );
-
-	// `var()` allows whitespace after the opening paren. The role reads its theme layer, so a value naming the role closes a cycle through the catalog entry: CSS marks every custom property in a cycle invalid at computed-value time, and the role's own fallback is not used, so the token resolves to nothing at all.
-	it( 'ignores a self-referential pointer padded with whitespace', () => {
-		expect(
-			themeOverrideVars( { gridStyles: { stroke: 'var( --a8c-charts-color-grid, #dbdbdb )' } } )
-				.vars
-		).toEqual( {} );
-	} );
-
-	it( 'still emits a value that merely mentions a different role', () => {
-		expect(
-			themeOverrideVars( { gridStyles: { stroke: 'var( --a8c-charts-color-axis, #dbdbdb )' } } )
-				.vars
-		).toEqual( {
-			'--a8c-charts-color-grid-theme': 'var( --a8c-charts-color-axis, #dbdbdb )',
-		} );
-	} );
-
-	// A mapped role can be a strict prefix of another custom property — a catalog role such as `--a8c-charts-color-label` of `--a8c-charts-color-label-axis`, the role's own theme layer, or a name the consumer defined themselves. A prefix match would read a legitimate cross-property pointer as a self-reference and silently drop the override, so the role must be followed by something that cannot continue an identifier.
-	it( 'does not mistake a longer property name for the role it guards', () => {
-		expect(
-			themeOverrideVars( {
-				xAxisLineStyles: { stroke: 'var(--a8c-charts-color-axis-emphasis, #000)' },
-			} ).vars
-		).toEqual( { '--a8c-charts-color-axis-theme': 'var(--a8c-charts-color-axis-emphasis, #000)' } );
-	} );
-
-	// `resolveCssVariable` also accepts a bare custom-property name with no `var()` wrapper, so `theme={ { gridStyles: { stroke: '--a8c-charts-color-grid' } } }` is legal input. It forms no cycle, so it must be caught explicitly or it survives as a literal string value and drops silently at the use site.
-	it( 'ignores a self-referential pointer written as a bare custom-property name', () => {
-		expect(
-			themeOverrideVars( { gridStyles: { stroke: '--a8c-charts-color-grid' } } ).vars
-		).toEqual( {} );
-	} );
-} );

package/src/providers/chart-context/test/with-catalog-pointers.test.ts

@@ -1,104 +0,0 @@
-import { mergeThemes } from '../../../utils';
-import { withCatalogPointers } from '../private/with-catalog-pointers';
-import { defaultTheme } from '../themes';
-import type { ChartTheme } from '../../../types';
-
-describe( 'withCatalogPointers', () => {
-	it( 'restores every overridden role to its catalog pointer, without mutating the input theme', () => {
-		const merged = mergeThemes( defaultTheme, {
-			backgroundColor: '#111',
-			gridStyles: { stroke: '#222' },
-			xAxisLineStyles: { stroke: '#333' },
-			xTickLineStyles: { stroke: '#444' },
-			svgLabelSmall: { fill: '#555' },
-			labelBackgroundColor: '#556',
-			labelTextColor: '#557',
-		} as Partial< ChartTheme > );
-
-		const result = withCatalogPointers( merged, [
-			'--a8c-charts-color-background',
-			'--a8c-charts-color-grid',
-			'--a8c-charts-color-axis',
-			'--a8c-charts-color-tick',
-			'--a8c-charts-color-label-axis',
-			'--a8c-charts-color-label-background',
-			'--a8c-charts-color-label-on-fill',
-		] );
-
-		expect( result.backgroundColor ).toBe( defaultTheme.backgroundColor );
-		expect( result.gridStyles.stroke ).toBe( defaultTheme.gridStyles.stroke );
-		expect( result.xAxisLineStyles.stroke ).toBe( defaultTheme.xAxisLineStyles.stroke );
-		expect( result.xTickLineStyles.stroke ).toBe( defaultTheme.xTickLineStyles.stroke );
-		expect( result.svgLabelSmall.fill ).toBe( defaultTheme.svgLabelSmall.fill );
-		expect( result.labelBackgroundColor ).toBe( defaultTheme.labelBackgroundColor );
-		expect( result.labelTextColor ).toBe( defaultTheme.labelTextColor );
-
-		expect( merged.backgroundColor ).toBe( '#111' );
-		expect( merged.gridStyles.stroke ).toBe( '#222' );
-	} );
-
-	it( 'leaves fields alone when no role was overridden', () => {
-		const merged = mergeThemes( defaultTheme, {
-			tickLength: 8,
-			leaderboardChart: { deltaColors: [ 'red', 'grey', 'green' ] },
-		} as Partial< ChartTheme > );
-
-		const result = withCatalogPointers( merged, [] );
-
-		expect( result.tickLength ).toBe( 8 );
-		expect( result.gridStyles.stroke ).toBe( defaultTheme.gridStyles.stroke );
-		// Not a mapped role, so its literal survives even when other roles are being restored.
-		expect( result.leaderboardChart.deltaColors ).toEqual( [ 'red', 'grey', 'green' ] );
-	} );
-
-	// The palette is restored as a whole, so a consumer's short array cannot shorten it. `mergeThemes` replaces arrays outright, and a two-entry palette would leave slots 3 to 5 unreadable — a CSS declaration of one of them would have no entry to resolve through.
-	it( 'restores the full five-slot palette from a shorter consumer array', () => {
-		const merged = mergeThemes( defaultTheme, {
-			colors: [ '#111', '#222' ],
-		} as Partial< ChartTheme > );
-
-		const result = withCatalogPointers( merged, [
-			'--a8c-charts-color-series-1',
-			'--a8c-charts-color-series-2',
-		] );
-
-		expect( result.colors ).toEqual( [
-			'var(--a8c-charts-color-series-1, #111)',
-			'var(--a8c-charts-color-series-2, #222)',
-			'var(--a8c-charts-color-series-3)',
-			'var(--a8c-charts-color-series-4)',
-			'var(--a8c-charts-color-series-5)',
-		] );
-	} );
-
-	// Each slot's restore rewrites the whole array, so restoring five of them must not wrap the pointers five times over.
-	it( 'restores the palette idempotently across every overridden slot', () => {
-		const merged = mergeThemes( defaultTheme, {
-			colors: [ '#111', '#222', '#333', '#444', '#555' ],
-		} as Partial< ChartTheme > );
-
-		const result = withCatalogPointers( merged, [
-			'--a8c-charts-color-series-1',
-			'--a8c-charts-color-series-2',
-			'--a8c-charts-color-series-3',
-			'--a8c-charts-color-series-4',
-			'--a8c-charts-color-series-5',
-		] );
-
-		expect( result.colors ).toEqual( [
-			'var(--a8c-charts-color-series-1, #111)',
-			'var(--a8c-charts-color-series-2, #222)',
-			'var(--a8c-charts-color-series-3, #333)',
-			'var(--a8c-charts-color-series-4, #444)',
-			'var(--a8c-charts-color-series-5, #555)',
-		] );
-	} );
-
-	// The literal is only reached where getComputedStyle resolves nothing, and the palette is the one field where falling back to the catalog default would be visible: every series would paint the same seeded blue.
-	it( 'keeps the consumer color as each pointer’s terminal literal, for SSR and jsdom', () => {
-		const merged = mergeThemes( defaultTheme, { colors: [ 'red' ] } as Partial< ChartTheme > );
-		const result = withCatalogPointers( merged, [ '--a8c-charts-color-series-1' ] );
-
-		expect( result.colors[ 0 ] ).toBe( 'var(--a8c-charts-color-series-1, red)' );
-	} );
-} );