test/cartesian/Bar/Bar.typed.spec.tsx (2)

64-285: Missing vi.useFakeTimers() — tests that render via rechartsTestRender may be sensitive to timers.

The coding guidelines require vi.useFakeTimers() in all tests due to Redux autoBatchEnhancer dependency on timers. While isAnimationActive={false} likely mitigates animation-related timer issues, the autoBatchEnhancer dependency could still cause flaky behavior. Consider adding a beforeEach with vi.useFakeTimers().

That said, the existing Area.typed.spec.tsx follows the same pattern without fake timers and appears to work, so this may be a pre-existing gap rather than something introduced here.

Proposed fix

+import { beforeEach, describe, it, vi } from 'vitest';
-import { describe, it } from 'vitest';
 import { Bar, BarChart, BarRectangleItem, getRelativeCoordinate } from '../../../src';
 import { rechartsTestRender } from '../../helper/createSelectorTestCase';
 import { expectBars, ExpectedBar } from '../../helper/expectBars';
 
 ...
 
 describe('Bar with strong typing', () => {
+  beforeEach(() => {
+    vi.useFakeTimers();
+  });
+
   describe('with all implicit types', () => {

As per coding guidelines: "Use vi.useFakeTimers() in all tests due to Redux autoBatchEnhancer dependency on timers and requestAnimationFrame"

---

144-193: Consider converting commented-out tests to a TODO or tracked issue.

These commented-out blocks document expected behavior if Bar supported data prop directly. While the explanatory comments are helpful, large commented-out code blocks can become stale. An alternative would be to track this as a GitHub issue and reference it here with a brief // TODO: comment.

This is a minor nit — the comments are well-documented and the intent is clear.