Reviewing files that changed from the base of the PR and between d3ccaac and cb1b631.

• test/cartesian/__snapshots__/ReferenceArea.spec.tsx.snap is excluded by !**/*.snap
• test/shape/__snapshots__/Sector.spec.tsx.snap is excluded by !**/*.snap

• scripts/snapshots/es6Files.txt (1 hunks)
• scripts/snapshots/libFiles.txt (1 hunks)
• scripts/snapshots/typesFiles.txt (1 hunks)
• src/shape/Polygon.tsx (2 hunks)
• src/shape/Rectangle.tsx (4 hunks)
• src/shape/Sector.tsx (6 hunks)
• src/shape/Trapezoid.tsx (1 hunks)
• src/util/DataUtils.ts (2 hunks)
• src/util/round.ts (1 hunks)
• test/cartesian/Area.animation.spec.tsx (1 hunks)
• test/cartesian/Bar.animation.spec.tsx (7 hunks)
• test/cartesian/Bar.spec.tsx (33 hunks)
• test/cartesian/ErrorBar.spec.tsx (2 hunks)
• test/cartesian/Funnel.animation.spec.tsx (5 hunks)
• test/cartesian/Line.animation.spec.tsx (5 hunks)
• test/cartesian/ReferenceArea.spec.tsx (2 hunks)
• test/cartesian/Scatter.animation.spec.tsx (1 hunks)
• test/cartesian/XAxis/XAxis.barSize.spec.tsx (3 hunks)
• test/cartesian/XAxis/XAxis.padding.spec.tsx (10 hunks)
• test/chart/BarChart.spec.tsx (26 hunks)
• test/chart/PieChart.spec.tsx (4 hunks)
• test/chart/RadialBarChart.spec.tsx (4 hunks)
• test/component/Legend.spec.tsx (4 hunks)
• test/helper/expectPieSectors.ts (2 hunks)
• test/polar/Pie.animation.spec.tsx (11 hunks)
• test/polar/Pie.spec.tsx (6 hunks)
• test/polar/PolarAngleAxis.spec.tsx (1 hunks)
• test/polar/Radar.animation.spec.tsx (13 hunks)
• test/polar/Radar.spec.tsx (2 hunks)
• test/polar/RadialBar.animation.spec.tsx (6 hunks)
• test/polar/RadialBar.spec.tsx (3 hunks)
• test/shape/Rectangle.animation.spec.tsx (2 hunks)
• test/util/round.spec.ts (1 hunks)

• GitHub Check: Build, Test, Pack
• GitHub Check: Analyze (javascript-typescript)

test/polar/RadialBar.animation.spec.tsx (1)

72-111: Rounded RadialBar path expectations look consistent with new path formatting

All updated d strings and expected path arrays simply reflect rounded coordinates while preserving path structure and test intent. No behavioral or assertion‑logic regressions spotted.

Also applies to: 88-113, 148-167, 260-283, 325-343

test/polar/PolarAngleAxis.spec.tsx (1)

1351-1352: Polygon axisLine path expectation correctly updated to rounded coordinates

The d attribute now uses rounded coordinates while keeping the same polygon structure and closure (...L250,54Z). This aligns with the new rounding behavior without changing test semantics.

test/polar/RadialBar.spec.tsx (1)

411-429: RadialBar sector path expectations correctly updated for rounded coordinates

The updated d strings preserve the same sector geometry while trimming numeric noise, matching the new rounding utility behavior. Test logic and coverage remain the same.

Also applies to: 797-813, 1049-1059

test/chart/RadialBarChart.spec.tsx (1)

69-88: Rounded sector and bar geometry expectations align with new rendering precision

The modified d path strings, label arc paths, and bar widths are consistent with rounding to a few decimal places while preserving overall geometry and test intent. No behavioral changes to the test suite beyond stricter, cleaner numeric expectations.

Also applies to: 141-160, 222-241, 264-283, 1649-1679, 1797-1825

test/cartesian/ErrorBar.spec.tsx (1)

1649-1679: Bar geometry expectations updated to match rounded widths and path data

The adjusted d attributes and width values now use rounded decimals, consistent with the new rounding behavior, while keeping bar positions and relative sizes intact. ErrorBar logic and axis‑domain tests remain unaffected.

Also applies to: 1797-1827

scripts/snapshots/libFiles.txt (1)

193-233: Snapshot manifest correctly includes new round util

Adding "lib/util/round.js" to libFiles.txt in the util section keeps snapshots aligned with the new exported utility and maintains the existing directory ordering.

test/helper/expectPieSectors.ts (1)

3-3: Pie sector angle helper now uses shared rounding, improving consistency

Importing round and applying it in calculateAngle makes the angle expectations robust to minor FP drift and aligns test calculations with the same rounding used in production SVG paths. The underlying angle math and parsing logic remain correct.

Also applies to: 32-46

scripts/snapshots/es6Files.txt (1)

232-232: LGTM! Snapshot entry for new rounding utility.

The addition of es6/util/round.js correctly tracks the new rounding utility module in the ES6 exports manifest.

src/util/DataUtils.ts (2)

3-3: LGTM! Import for new rounding utility.

The import statement correctly brings in the round function needed for the interpolation rounding below.

---

108-108: LGTM! Rounding applied to interpolation results.

The addition of round() to the interpolation result is appropriate for SVG/DOM coordinate values and addresses the floating-point precision differences between Node versions mentioned in the PR objectives.

test/cartesian/Scatter.animation.spec.tsx (1)

316-318: LGTM! Test expectations updated for rounded coordinates.

The cy values have been correctly updated to reflect the rounded numeric output from the new rounding utilities. The precision is consistent with the 4-decimal-place rounding applied throughout the PR.

scripts/snapshots/typesFiles.txt (1)

232-232: LGTM! Type declaration snapshot entry.

The addition of types/util/round.d.ts correctly tracks the type declarations for the new rounding utility.

test/component/Legend.spec.tsx (1)

991-1099: LGTM! Test expectations updated for rounded Bar coordinates.

The updated assertions reflect the rounded numeric values produced by the new rounding utilities in the Rectangle/Bar shape components. All values are consistently rounded to 4 decimal places, matching the precision chosen in the PR.

test/cartesian/Funnel.animation.spec.tsx (1)

102-169: LGTM! Funnel trapezoid path expectations updated for rounding.

The SVG path data strings have been correctly updated to reflect the rounded coordinates generated by the roundTemplateLiteral utility used in the Trapezoid shape component. All values consistently use 4-decimal-place precision.

test/cartesian/Bar.animation.spec.tsx (1)

211-442: LGTM! Bar animation expectations updated for rounded values.

The test expectations for heights, y-coordinates, and path data have been correctly updated to match the rounded output from the Rectangle shape component. All values consistently use 4-decimal-place precision, aligning with the rounding utilities introduced in this PR.

The minor wording improvement on line 275 also improves readability.

test/cartesian/Area.animation.spec.tsx (1)

411-412: LGTM! Area dot coordinate expectations updated for rounding.

The cy coordinate strings have been correctly updated to reflect the rounded values produced by the interpolation function in DataUtils. The precision is consistent with the 4-decimal-place rounding applied throughout the PR.

src/shape/Polygon.tsx (1)

9-9: Polygon path rounding via roundTemplateLiteral looks correct

Using roundTemplateLiteral here cleanly rounds only the numeric coordinates while preserving the accumulated path string and command characters, without changing control flow or connectNulls semantics. This aligns with the PR goal of DOM-only rounding.

Also applies to: 52-52

test/polar/Radar.spec.tsx (1)

40-46: Updated Radar polygon d expectations match new rounded path output

The new d strings use the compact M250,167.68L...Z form with rounded coordinates, consistent with Polygon now building paths via roundTemplateLiteral. No behavioral change to the tests beyond formatting.

Also applies to: 60-66

src/shape/Trapezoid.tsx (1)

14-24: Rounding in getTrapezoidPath is consistent and non-invasive

Switching to roundTemplateLiteral for each segment correctly rounds all numeric coordinates while preserving the existing trapezoid geometry and control flow. This keeps Trapezoid aligned with the other rounded shapes.

test/chart/BarChart.spec.tsx (1)

337-447: Bar expectBars snapshots correctly updated for rounded geometry

All modified expectBars cases now assert rounded coordinates and dimensions (up to 4 decimals), matching the new Rectangle/rounding behavior while leaving test intent and chart semantics unchanged. Nothing here suggests functional regressions.

Also applies to: 465-531, 563-629, 647-713, 731-765, 1004-1070, 1106-1172, 1769-1835, 1933-2037, 2192-2407, 2573-2686, 2699-2841, 2854-2919, 2933-2999, 3012-3077, 3092-3156, 3169-3233

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

122-168: XAxis padding bar expectations aligned with rounded Rectangle output

The modified expectBars expectations for the different padding modes now match the rounded Rectangle geometry (x/y/d/height/width), with no change to how padding logic or selector behavior is tested.

Also applies to: 211-268, 310-367, 409-467, 508-565, 607-665

test/polar/Pie.spec.tsx (1)

60-67: Pie sector angle and path expectations updated for rounding without changing semantics

Rounding pageDataSectorPaths coordinates and the endAngle values in active-shape/event assertions to 4 decimals matches the new Pie/Sector rounding utilities while preserving payload structure and all behavioral checks.

Also applies to: 335-412, 1872-2128

src/shape/Rectangle.tsx (1)

15-25: Rectangle rounding integration looks sound and localized to DOM output

• roundedWidth/roundedHeight are used only for maxRadius and sign, bringing radius capping in line with the rendered (rounded) dimensions while changing only sub‑pixel cases.
• Converting all path construction to roundTemplateLiteral and adding rounded x/y/width/height attributes in the non-update branch cleanly normalizes DOM output without altering validation or animation control flow.
• Animated rectangles still route through getRectanglePath, so their d strings are rounded as well, even though x/y/width/height attributes are omitted there (tests appear to rely on the non-animated cases).

Also applies to: 34-72, 171-184

test/shape/Rectangle.animation.spec.tsx (2)

234-240: Test expectations correctly updated to reflect 4-decimal rounding.

The animated path values (e.g., 127.8959, 139.6508, 144.8153) now reflect the rounding applied by roundTemplateLiteral in Rectangle.tsx. These intermediate animation frames demonstrate consistent precision across Node versions.

---

332-347: Animation path expectations for both increase and decrease transitions look correct.

The rounded path coordinates maintain visual fidelity while ensuring cross-Node-version consistency. Both the width-increase (lines 334-337) and width-decrease (lines 343-346) animations show proper interpolation with 4-decimal precision.

test/cartesian/ReferenceArea.spec.tsx (3)

99-99: Path data correctly rounded.

The d attribute now uses rounded values consistent with the Rectangle component's rounding implementation.

---

363-366: Numeric attributes rounded to 4 decimal places.

The x and width attributes now show 112.2727 and 59.0909 respectively, matching the rounding precision applied in the Rectangle component.

---

434-437: Custom shape elements retain full precision as expected.

When shape is a React Element (line 388), the props are injected directly without going through Rectangle's path rendering, so these attributes (x: '112.27272727272728', width: '59.09090909090909') correctly retain their original precision. This is the expected behavior since only the Rectangle's internal path construction uses rounding.

src/shape/Sector.tsx (3)

9-9: Import of rounding utility is appropriate.

The roundTemplateLiteral import enables consistent numeric rounding across all path string constructions in this file.

---

59-73: Path construction in getSectorPath correctly uses rounding.

The outer arc path (lines 59-63), inner arc path (lines 68-71), and center fallback (line 73) all use roundTemplateLiteral to ensure consistent numeric precision in the SVG path data.

---

123-142: Corner radius path segments correctly use rounding.

Both the forceCornerRadius return path (lines 123-126), the main sector path with corners (lines 138-142), and the inner arc segments (lines 181-186) properly apply roundTemplateLiteral for consistent precision.

Also applies to: 181-186

test/cartesian/XAxis/XAxis.barSize.spec.tsx (2)

40-97: Bar position expectations correctly updated with rounded values.

The expected bar attributes (d, height, x, y) now use 4-decimal precision (e.g., 65.8377, 144.8179, 120.5556), consistent with the rounding applied in the Rectangle component's path generation.

---

211-219: Single data point bar expectations correctly rounded.

These test cases for single data points with various barSize configurations show properly rounded coordinates and dimensions.

Also applies to: 267-275

test/cartesian/Line.animation.spec.tsx (4)

218-218: Stroke-dasharray expectation is correct.

The value '10px 90px' represents the expected stroke-dasharray at 10% animation progress.

---

371-371: Dashed line stroke-dasharray format updated.

The expected value uses comma separation ('7px, 3px, 0px, 90px') consistent with the dashed stroke animation pattern.

---

599-627: Animated dot positions correctly show 4-decimal precision.

The cy values during animation (e.g., 32.7794, 38.4836, 40.6985, 46.139) reflect the rounded interpolated coordinates, ensuring consistent output across Node versions.

---

766-794: Additional animation frame expectations correctly updated.

These dot position expectations maintain the 4-decimal precision pattern throughout the animation tests, covering both the "interrupting initial animation" and "interaction after initial animation completes" scenarios.

Also applies to: 1124-1162

test/cartesian/Bar.spec.tsx (4)

73-114: Horizontal bar layout expectations correctly rounded.

The bar dimension and position values (e.g., 413.3333, 81.6667, 331.6667, 163.3333) now use consistent 4-decimal precision, matching the Rectangle component's rounding behavior.

---

178-219: Vertical bar layout expectations correctly rounded.

The width values (e.g., 71.6667, 143.3333, 286.6667, 358.3333) for vertical bars show proper rounding, maintaining visual accuracy while ensuring cross-Node-version consistency.

---

1165-1182: Zero-value bar handling shows appropriate precision.

The small bar heights (e.g., 0.046 for near-zero values) demonstrate that the rounding doesn't eliminate visually meaningful precision for edge cases.

---

1444-1463: Stacked bar and tooltip interaction tests correctly updated.

The stacked bar position expectations maintain the 4-decimal precision pattern, ensuring tooltip interactions work correctly with the rounded coordinates.

Also applies to: 1496-1521, 1536-1555, 1750-1759

test/chart/PieChart.spec.tsx (4)

41-41: Single sector path correctly rounded.

The arc coordinates in the path data (285,205.0014) show proper 4-decimal precision for a full-circle sector.

---

67-72: Angle values normalized correctly.

The angle expectations now use canonical representations:

• startAngle: 0 instead of -0 (line 68)
• endAngle: 0 instead of 360 (line 71) - mathematically equivalent for a full rotation

This aligns with the round() utility's -0 to 0 normalization mentioned in the AI summary.

---

91-98: Sector arc coordinates properly rounded.

All sector path data now uses 4-decimal precision for coordinates (e.g., 202.3541,125.0438, 129.4422,178.7128), ensuring consistent rendering across different Node.js versions.

---

218-225: Cell-based sector rendering expectations correctly updated.

The path data for sectors rendered with explicit <Cell> components shows the same 4-decimal rounding, confirming the rounding is applied consistently regardless of how sectors are configured.

test/util/round.spec.ts (1)

4-57: Round / roundTemplateLiteral test matrix looks solid and matches util semantics

The test suite exercises default/custom precision, negative numbers and -0, small/large values, and typical SVG path/template use cases, including string passthrough and spacing. This is in line with the coverage expectations for new utilities and should give high confidence in the behavior.

Based on learnings, this looks consistent with the “aim for 100% coverage” goal for new test code.

Also applies to: 60-112

test/polar/Pie.animation.spec.tsx (3)

22-26: Updated final sector paths and static angle expectations align with 4‑decimal rounding

The finalSectorPaths and the non‑animated expectPieSectorAngles expectations now use coordinates/angles rounded to 4 decimal places and remain internally consistent (paths close correctly, angles describe a full circle with the last sector wrapping via endAngle: 0). This matches the new rounding behavior used across the shapes.

Also applies to: 208-216

---

272-303: Animated path/angle expectations for the simple props case look consistent with new rounding

The intermediate d attributes and angle arrays in should render sectors with animation and should render sectors with animated angles are updated to 4‑decimal values, with each step showing smooth progression and sectors that still partition the circle correctly. No logic changes beyond the expected numeric normalization.

Also applies to: 306-333

---

363-440: Angle expectations for dataKey/data array/visibility interactions correctly reflect rounded interpolation

Across the interaction tests (changing dataKey, changing data array, forcing re‑animation via key, and hide/show), the updated angle sequences now:

• Use 4‑decimal precision.
• Maintain sector continuity (startAngle of each sector equals the previous sector’s endAngle or the wrapped equivalent).
• Preserve the expected qualitative behavior (growth from a fixed start for the first sector, rearrangements, and wraparound with endAngle: 0 for a full circle).

These updates look mechanically consistent with the new rounding behavior and the helper used in expectPieSectors.

Also applies to: 487-510, 538-607, 644-680