@spider-analyzer/timeline 5.0.4 → 5.0.5

package/CHANGELOG.md

@@ -1,3 +1,20 @@
+## 5.0.5
+
+- Fix: compute intervalMs defensively in `getItems`. When d3's
+  `xAxis.ticks(N)` momentarily returned fewer than 2 entries (sparse
+  tick generation during the first render, while layout is still
+  settling), the previous code did `moment(ticks[1]).diff(moment(ticks[0]))`
+  with `ticks[1]` undefined. `moment(undefined)` is "now", so the diff
+  went negative, `_max` picked `smallestResolution`, and the very first
+  `onLoadHisto` asked for a 15 ms resolution over the whole domain —
+  flooding the backend. Any subsequent gesture (scroll, resize) produced
+  a correct interval, matching the user-observed "scrolling fixes it"
+  behavior.
+
+  Fix: when ticks are sparse, fall back to `domainSpan / tickCount`
+  instead of trusting ticks[1]−ticks[0]. Same nice-interval behavior on
+  the happy path, no regression when d3 hasn't produced enough ticks.
+
 ## 5.0.4
 
 - Fix: memoize the moment-typed props built by the outer TimeLine

package/dist/index.js

@@ -2081,9 +2081,11 @@ var TimeLineInner = react.forwardRef(function TimeLine(props, ref) {
     const xAxis = d3Scale.scaleTime().domain([domain2.min, domain2.max]).range([0, histoWidth2]);
     xAxis.clamp(true);
     xAxisRef.current = xAxis;
-    const ticks2 = xAxis.ticks(floor(histoWidth2 / p.xAxis.spaceBetweenTicks));
+    const tickCount = floor(histoWidth2 / p.xAxis.spaceBetweenTicks);
+    const ticks2 = xAxis.ticks(tickCount);
+    const tickIntervalMs = ticks2.length >= 2 ? ticks2[1].getTime() - ticks2[0].getTime() : (+domain2.max - +domain2.min) / Math.max(tickCount, 1);
     const intervalMs = max([
-      round(moment_shim_default(ticks2[1]).diff(moment_shim_default(ticks2[0])) / p.xAxis.barsBetweenTicks),
+      round(tickIntervalMs / p.xAxis.barsBetweenTicks),
       propsRef.current.smallestResolution.asMilliseconds()
     ]);
     patchState({ histoWidth: histoWidth2, isActive: true, ticks: ticks2 });