src/cartesian/CartesianAxis.tsx (1)

393-395: Add a regression test to guard the user-provided textAnchor behaviour.

No test file was included in this PR. The regression in #7027 was not caught by the existing test suite, so a targeted test (e.g., verifying that a tick <Text> renders with the explicitly-passed textAnchor rather than the orientation-derived default) would prevent it from recurring.

As per coding guidelines: "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 `@src/cartesian/CartesianAxis.tsx` around lines 393 - 395, Add a regression
unit test that mounts/renders the CartesianAxis component and verifies that when
axisProps.textAnchor is explicitly provided the tick <Text> element uses that
value instead of the orientation-derived default from getTickTextAnchor; locate
the behavior around the textAnchor assignment in CartesianAxis (the const
textAnchor = (axisProps.textAnchor as TextAnchor) ??
getTickTextAnchor(orientation, mirror);) and write an assertion that a tick's
rendered text element has the expected textAnchor attribute when
axisProps.textAnchor is set, plus a complementary case where
axisProps.textAnchor is undefined to ensure the fallback to getTickTextAnchor
still works.

test/cartesian/CartesianAxis.spec.tsx (2)

360-403: Consider adding a vertical-axis (left/right orientation) textAnchor test to match PR scope.

The PR title and linked issue mention both XAxis and YAxis. The fix in CartesianAxis.tsx applies to all orientations, but both new tests only cover orientation="bottom". A parallel test asserting that a user-provided textAnchor on a vertical axis (e.g., orientation="left") is also respected would give complete regression coverage for the stated fix.

🤖 Prompt for AI Agents

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

In `@test/cartesian/CartesianAxis.spec.tsx` around lines 360 - 403, Add a parallel
test in CartesianAxis.spec.tsx that renders <CartesianAxis> with a vertical
orientation (e.g., orientation="left" or "right") inside <Surface> using the
same ticks, exampleScale and viewBox, passing a user-provided textAnchor (for
example "start"), then query the tick elements by the
'.recharts-cartesian-axis-tick-value' selector and assert each tick has the
expected 'text-anchor' attribute; mirror the existing horizontal tests (the ones
using orientation="bottom") but change orientation and positioning props so the
test targets the vertical-axis code paths in CartesianAxis.

---

360-403: Missing vi.useFakeTimers() and vi.runOnlyPendingTimers() in both new tests.

The coding guidelines require vi.useFakeTimers() in all tests and vi.runOnlyPendingTimers() after renders (when not using createSelectorTestCase). Both new tests omit these. While none of the pre-existing tests in this file include them either, that is a pre-existing gap — the new tests being added now should follow the guideline.

♻️ Proposed fix

+import { beforeEach, afterEach } from 'vitest';

+  beforeEach(() => {
+    vi.useFakeTimers();
+  });
+
+  afterEach(() => {
+    vi.useRealTimers();
+  });

   it('Respects user-provided textAnchor prop on horizontal axis', () => {
     const { container } = render(
       <Surface width={500} height={500}>
         <CartesianAxis
           orientation="bottom"
           y={100}
           width={400}
           height={50}
           viewBox={{ x: 0, y: 0, width: 500, height: 500 }}
           ticks={ticks}
           textAnchor="start"
           scale={exampleScale}
         />
       </Surface>,
     );
+    vi.runOnlyPendingTimers();

     const tickTexts = container.querySelectorAll('.recharts-cartesian-axis-tick-value');
     expect(tickTexts).toHaveLength(5);
     tickTexts.forEach(text => {
       expect(text).toHaveAttribute('text-anchor', 'start');
     });
   });

   it('Uses default textAnchor when not provided', () => {
     const { container } = render(
       <Surface width={500} height={500}>
         <CartesianAxis
           orientation="bottom"
           y={100}
           width={400}
           height={50}
           viewBox={{ x: 0, y: 0, width: 500, height: 500 }}
           ticks={ticks}
           scale={exampleScale}
         />
       </Surface>,
     );
+    vi.runOnlyPendingTimers();

     const tickTexts = container.querySelectorAll('.recharts-cartesian-axis-tick-value');
     expect(tickTexts).toHaveLength(5);
     tickTexts.forEach(text => {
       expect(text).toHaveAttribute('text-anchor', 'middle');
     });
   });

As per coding guidelines: "Use vi.useFakeTimers() in all tests due to Redux autoBatchEnhancer dependency on timers and requestAnimationFrame" and "Call vi.runOnlyPendingTimers() to advance timers after renders when not using createSelectorTestCase helper".

🤖 Prompt for AI Agents

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

In `@test/cartesian/CartesianAxis.spec.tsx` around lines 360 - 403, Add test timer
setup and advancement to both new tests ("Respects user-provided textAnchor prop
on horizontal axis" and "Uses default textAnchor when not provided"): call
vi.useFakeTimers() at the start of each it block before render and call
vi.runOnlyPendingTimers() immediately after the render(...) completes so pending
timers/RAF are flushed; ensure this is applied inside the same it blocks
surrounding the render of <CartesianAxis ... /> to satisfy the Redux
autoBatchEnhancer and requestAnimationFrame requirements.