src/state/cartesianAxisSlice.ts (1)

75-75: Consider using a more specific type or unknown for tick.

The tick property uses TickProp<any>, which retains any in the type system. Per coding guidelines, any should be avoided.

However, based on learnings, DataKey<any> is an intentional exception while proper typing is being developed. If this usage follows the same pattern for shared internal state types (since TicksSettings is used by both XAxis and YAxis with different content props), this may be acceptable as an interim measure.

If intentional, consider adding a comment similar to other exceptions explaining why any is used here.

test/cartesian/YAxis/YAxis.tick.spec.tsx (1)

132-135: Consider using YAxisTickContentProps instead of any for consistency.

These custom tick components use any for props typing, which conflicts with the coding guideline to avoid any. While the test is intentionally loose to verify prop passing, using the explicit type would be more consistent with the PR's objective of replacing any with explicit types.

However, since this is a test file and the assertion is specifically checking a subset of props (props.padding), the any usage is acceptable for test simplicity.

Optional: Use explicit type for consistency

-      const CustomYAxisTick = (props: any) => {
+      const CustomYAxisTick = (props: YAxisTickContentProps) => {
         expect(props.padding).toEqual(expectedPadding);
         return <text>Custom Tick</text>;
       };

Also applies to: 149-152, 182-185

test/cartesian/XAxis/XAxis.tick.spec.tsx (1)

122-125: Same any usage pattern as YAxis tests.

These custom tick components use any for props typing. As noted in the YAxis review, this is acceptable for test simplicity, though using XAxisTickContentProps would be more consistent with the PR's objective.

Also applies to: 139-142, 172-175

src/util/types.ts (1)

36-38: Use type-only imports for the new axis/text types.

These are only used in type positions, so import type avoids the circular dependency with cartesianAxisSlice and reduces risk of bundler issues.

♻️ Suggested change

-import { XAxisOrientation, XAxisPadding, YAxisOrientation, YAxisPadding } from '../state/cartesianAxisSlice';
-import { TextAnchor, TextVerticalAnchor } from '../component/Text';
+import type { XAxisOrientation, XAxisPadding, YAxisOrientation, YAxisPadding } from '../state/cartesianAxisSlice';
+import type { TextAnchor, TextVerticalAnchor } from '../component/Text';

test/cartesian/YAxis/YAxis.tick.spec.tsx (1)

38-39: Confirm fake timers are enabled for this suite.
If this isn’t already handled in test setup, consider enabling vi.useFakeTimers() for this describe block to avoid rAF/timer flakiness. As per coding guidelines, please ensure fake timers are enabled for test suites.