@fusion.dev/helix-core 0.51.0 → 0.52.1

package/custom-elements.json

@@ -9486,13 +9486,12 @@
             },
             {
               "name": "curve",
-              "default": "'straight'",
               "type": {
                 "text": "Curve"
               }
             }
           ],
-          "description": "Builds an SVG path through a set of points.\n\nShared by every chart that draws a line, so the choice of curve is one\nimplementation rather than one per chart. Pure: it takes points and returns a\nstring, and knows nothing about elements or lifecycles.\n\n`straight` joins the readings and claims nothing between them, which is why\nit is the default. `smooth` is easier to follow across a long series and\ninvents the values in between, so it is a reading aid rather than a neutral\none. `step` claims the opposite, that a reading holds until the next one, and\nchanges at the midpoint rather than at either end, since a chart's x axis is\nan order and neither neighbor has a better claim on the moment it moved.\n\nFewer than two points is an empty string rather than a partial path: one\nreading is not a line, and `M0,0` alone draws nothing while still being a\npath element that looks like it should."
+          "description": "Builds an SVG path through a set of points.\n\nShared by every chart that draws a line, so the choice of curve is one\nimplementation rather than one per chart. Pure: it takes points and returns a\nstring, and knows nothing about elements or lifecycles.\n\n`straight` joins the readings and claims nothing between them. `smooth` is\neasier to follow across a long series and invents the values in between, so\nit is a reading aid rather than a neutral one. `step` claims the opposite,\nthat a reading holds until the next one, and changes at the midpoint rather\nthan at either end, since a chart's x axis is an order and neither neighbor\nhas a better claim on the moment it moved.\n\n**Two resting curves in this library, and what separates them is what the\nmark claims.** A line claims a position, so `LineChart` and `Sparkline` rest\nat `smooth`: the invention is bounded, the interpolation never leaves the\nband the data sets, and the smoothed line is the easier one to follow. A\nstacked band claims an amount, and a curve fitted through one sum can pass\nunder the curve fitted through the sum beneath it, so `AreaChart` rests at\n`straight`, where readings that are ordered stay ordered everywhere between.\nEach family publishes its own resting value on its own `curve`, because the\nreference page is generated from those blocks and a consumer does not read\nthis file; this is the one place that holds both halves side by side.\n\n**No default here, which is the point.** A default would be a third resting\ncurve, silently right for one caller and silently wrong for the other, and\nthe two above are already an argument somebody has to have read to pick a\nside. Every caller passes the value.\n\nFewer than two points is an empty string rather than a partial path: one\nreading is not a line, and `M0,0` alone draws nothing while still being a\npath element that looks like it should."
         }
       ],
       "exports": [

package/dist/utils/line-path/line-path.d.ts

@@ -9,15 +9,31 @@ export type Point = readonly [number, number];
  * implementation rather than one per chart. Pure: it takes points and returns a
  * string, and knows nothing about elements or lifecycles.
  *
- * `straight` joins the readings and claims nothing between them, which is why
- * it is the default. `smooth` is easier to follow across a long series and
- * invents the values in between, so it is a reading aid rather than a neutral
- * one. `step` claims the opposite, that a reading holds until the next one, and
- * changes at the midpoint rather than at either end, since a chart's x axis is
- * an order and neither neighbor has a better claim on the moment it moved.
+ * `straight` joins the readings and claims nothing between them. `smooth` is
+ * easier to follow across a long series and invents the values in between, so
+ * it is a reading aid rather than a neutral one. `step` claims the opposite,
+ * that a reading holds until the next one, and changes at the midpoint rather
+ * than at either end, since a chart's x axis is an order and neither neighbor
+ * has a better claim on the moment it moved.
+ *
+ * **Two resting curves in this library, and what separates them is what the
+ * mark claims.** A line claims a position, so `LineChart` and `Sparkline` rest
+ * at `smooth`: the invention is bounded, the interpolation never leaves the
+ * band the data sets, and the smoothed line is the easier one to follow. A
+ * stacked band claims an amount, and a curve fitted through one sum can pass
+ * under the curve fitted through the sum beneath it, so `AreaChart` rests at
+ * `straight`, where readings that are ordered stay ordered everywhere between.
+ * Each family publishes its own resting value on its own `curve`, because the
+ * reference page is generated from those blocks and a consumer does not read
+ * this file; this is the one place that holds both halves side by side.
+ *
+ * **No default here, which is the point.** A default would be a third resting
+ * curve, silently right for one caller and silently wrong for the other, and
+ * the two above are already an argument somebody has to have read to pick a
+ * side. Every caller passes the value.
  *
  * Fewer than two points is an empty string rather than a partial path: one
  * reading is not a line, and `M0,0` alone draws nothing while still being a
  * path element that looks like it should.
  */
-export declare const linePath: (points: readonly Point[], curve?: Curve) => string;
+export declare const linePath: (points: readonly Point[], curve: Curve) => string;

package/dist/utils/line-path/line-path.js

@@ -32,7 +32,7 @@ const tangents = (xs, ys) => {
     }
     return slope;
 };
-export const linePath = (points, curve = 'straight') => {
+export const linePath = (points, curve) => {
     if (points.length < 2) {
         return '';
     }

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@fusion.dev/helix-core",
   "description": "Helix element primitives: base classes, mixins, decorators, utilities.",
-  "version": "0.51.0",
+  "version": "0.52.1",
   "license": "MIT",
   "author": "Ross Sheppard <ross.sheppard@fusion.dev>",
   "repository": {
@@ -34,12 +34,12 @@
   "bugs": "https://github.com/project-fusion/fusion/issues",
   "dependencies": {
     "@floating-ui/dom": "^1.8.0",
-    "@fusion.dev/helix-icons": "0.51.0"
+    "@fusion.dev/helix-icons": "0.52.1"
   },
   "devDependencies": {
     "@custom-elements-manifest/analyzer": "^0.11.0",
-    "@fusion.dev/helix-cem": "0.51.0",
-    "@fusion.dev/helix-testing": "0.51.0",
+    "@fusion.dev/helix-cem": "0.52.1",
+    "@fusion.dev/helix-testing": "0.52.1",
     "lit": "^3.2.1"
   },
   "homepage": "https://fusion.dev",