test/util/ChartUtils.spec.tsx (1)

439-467: Nice regression coverage; add explicit null case for completeness.

The suite is strong for 0/'' preservation and fallback paths. Consider adding a null input assertion to fully lock in the nullish contract introduced in Line [705].

Suggested test addition

 describe('getTooltipNameProp', () => {
@@
   it('should fall back to string dataKey when name is undefined', () => {
     expect(getTooltipNameProp(undefined, 'revenue')).toBe('revenue');
   });
+
+  it('should fall back to string dataKey when name is null', () => {
+    expect(getTooltipNameProp(null, 'revenue')).toBe('revenue');
+  });
@@
 });

As per coding guidelines: test/**/*.{test,spec}.{ts,tsx}: Aim for 100% unit test code coverage when writing new code.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@test/util/ChartUtils.spec.tsx` around lines 439 - 467, Add explicit tests
covering name === null for getTooltipNameProp: verify that
getTooltipNameProp(null, 'revenue') falls back to the string dataKey
('revenue'), getTooltipNameProp(null, (e) => e) returns undefined when dataKey
is a function, and getTooltipNameProp(null, null) returns undefined; add these
assertions to the existing describe('getTooltipNameProp') block in
ChartUtils.spec.tsx so the null branch of the nullish contract (introduced
around line 705) is exercised.