@graphysdk/viz-engine 0.0.1-plugins.1 → 0.0.1-plugins.2

package/dist/extensions.d.ts

@@ -977,6 +977,13 @@ declare interface PolarCoordSystem {
     axisMapping: AxisMapping;
     /** Donut hole radius as a fraction of the outer radius (0-1). 0 for a full pie. */
     innerRadius: number;
+    /**
+     * Angular offset, in radians, applied to every angular position — the spec's `startAngle` (degrees)
+     * converted once at setup. The polar guide renderer recovers a tick's angle as `position * 2π +
+     * startAngle`, matching the angular transform the coord applies to the data, so spokes/labels align
+     * with the painted marks.
+     */
+    startAngle: number;
 }
 
 /**
@@ -1179,8 +1186,14 @@ declare interface SortTransformInput {
  * instead provides a render-side hit-test function (injected per-instance through the renderer),
  * and the engine resolves the observation it returns against the declared identity key. Only the
  * kind rides in the compiled spec — the closure never crosses the serialisable boundary.
+ *
+ * `polar-points` is the polar refinement of `points` (a radar's vertices read in polar). The cursor
+ * and the vertices live in incompatible spaces for the cartesian nearest query — vertices are
+ * `(angle, radius)`, the cursor is plot-local `[0,1]` — so the polar query converts each at query
+ * time (no stored cartesian, no Delaunay), staying correct across resizes. Geoms never declare it; a
+ * polar coord refines a `points`-natural mark to it during the coord transform.
  */
-export declare type SpatialIndexKind = 'buckets' | 'rects' | 'points' | 'arcs' | 'noop' | 'render-hit-test';
+export declare type SpatialIndexKind = 'buckets' | 'rects' | 'points' | 'arcs' | 'noop' | 'render-hit-test' | 'polar-points';
 
 /**
  * Discriminated union of all resolved stat specs (post-resolution).