src/polar/PolarRadiusAxis.tsx (1)

200-200: Type fix correctly aligns with implementation.

This change properly narrows the ticks prop type from TickItem (object with coordinate, value, index, etc.) to AxisTick (primitive number | string), matching what the implementation actually accepts. This resolves issue #4668 where users had to cast numeric arrays to satisfy the incorrect type.

Consider adding a JSDoc comment to document this prop for the API documentation:

📝 Optional: Add JSDoc for the ticks prop

   tick?: TickProp<BaseTickContentProps>;
+  /**
+   * Set the values of axis ticks manually.
+   * When this prop is set, the axis will use these values instead of computing them from the data.
+   */
   ticks?: ReadonlyArray<AxisTick>;

🤖 Prompt for AI Agents

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

In `@src/polar/PolarRadiusAxis.tsx` at line 200, The ticks prop type is currently
incorrect (was using TickItem) and needs to be narrowed to AxisTick to match the
implementation that accepts primitive tick values; update the ticks declaration
in PolarRadiusAxis (the prop/interface where "ticks" is defined) to use
ReadonlyArray<AxisTick> instead of TickItem[] (or similar), and add a concise
JSDoc above the ticks prop describing it accepts an array of primitive tick
values (number | string) so API docs reflect the change.