@fusion.dev/helix-core 0.58.0 → 0.58.1

package/custom-elements.json

@@ -6471,6 +6471,14 @@
             "module": "./utils/value-as/value-as.js"
           }
         },
+        {
+          "kind": "js",
+          "name": "isDateValue",
+          "declaration": {
+            "name": "isDateValue",
+            "module": "./utils/value-as/value-as.js"
+          }
+        },
         {
           "kind": "js",
           "name": "numberAsValue",
@@ -11276,6 +11284,24 @@
           ],
           "description": "The date a `YYYY-MM-DD` value names, at midnight UTC, or `null`.\n\nThe range check is not decoration. `2026-02-31` matches the pattern and\n`Date.UTC` rolls it forward to 3 March, so without reading the parts back a\ncontrol would report a date the reader never typed and never saw."
         },
+        {
+          "kind": "function",
+          "name": "isDateValue",
+          "return": {
+            "type": {
+              "text": "boolean"
+            }
+          },
+          "parameters": [
+            {
+              "name": "value",
+              "type": {
+                "text": "string"
+              }
+            }
+          ],
+          "description": "Whether a value names a real day, which is the shape *and* the range.\n\nThe predicate form of the conversion above, here rather than in a family\nbecause a family writing its own gets the shape right and the range wrong.\nTwo did: one tested `\\d{4}-\\d{2}-\\d{2}` and reported `2026-02-31` as whole\nwhile its own `valueAsDate` answered `null`, and the other guarded\n`Number.isNaN(date.getTime())`, which never fires, `Date.UTC(2026, 1, 31)`\nbeing a perfectly good third of March."
+        },
         {
           "kind": "function",
           "name": "dateAsValue",
@@ -11376,6 +11402,14 @@
             "module": "src/utils/value-as/value-as.ts"
           }
         },
+        {
+          "kind": "js",
+          "name": "isDateValue",
+          "declaration": {
+            "name": "isDateValue",
+            "module": "src/utils/value-as/value-as.ts"
+          }
+        },
         {
           "kind": "js",
           "name": "dateAsValue",

package/dist/index.d.ts

@@ -64,5 +64,5 @@ export { slotFilled } from './utils/slot-filled/slot-filled.js';
 export { tellDisclosure } from './utils/tell-disclosure/tell-disclosure.js';
 export { subscribe } from './utils/ticker/ticker.js';
 export { type HelixStatusTone, TONE_MARKS, type ToneMark, toneMark, } from './utils/tone-marks/tone-marks.js';
-export { dateAsValue, numberAsValue, timeAsValue, valueAsDate, valueAsNumber, valueAsTime, } from './utils/value-as/value-as.js';
+export { dateAsValue, isDateValue, numberAsValue, timeAsValue, valueAsDate, valueAsNumber, valueAsTime, } from './utils/value-as/value-as.js';
 export { writtenList } from './utils/written-list/written-list.js';

package/dist/index.js

@@ -64,5 +64,5 @@ export { slotFilled } from './utils/slot-filled/slot-filled.js';
 export { tellDisclosure } from './utils/tell-disclosure/tell-disclosure.js';
 export { subscribe } from './utils/ticker/ticker.js';
 export { TONE_MARKS, toneMark, } from './utils/tone-marks/tone-marks.js';
-export { dateAsValue, numberAsValue, timeAsValue, valueAsDate, valueAsNumber, valueAsTime, } from './utils/value-as/value-as.js';
+export { dateAsValue, isDateValue, numberAsValue, timeAsValue, valueAsDate, valueAsNumber, valueAsTime, } from './utils/value-as/value-as.js';
 export { writtenList } from './utils/written-list/written-list.js';

package/dist/utils/value-as/value-as.d.ts

@@ -6,6 +6,17 @@
  * control would report a date the reader never typed and never saw.
  */
 export declare const valueAsDate: (value: string) => Date | null;
+/**
+ * Whether a value names a real day, which is the shape *and* the range.
+ *
+ * The predicate form of the conversion above, here rather than in a family
+ * because a family writing its own gets the shape right and the range wrong.
+ * Two did: one tested `\d{4}-\d{2}-\d{2}` and reported `2026-02-31` as whole
+ * while its own `valueAsDate` answered `null`, and the other guarded
+ * `Number.isNaN(date.getTime())`, which never fires, `Date.UTC(2026, 1, 31)`
+ * being a perfectly good third of March.
+ */
+export declare const isDateValue: (value: string) => boolean;
 /** The `YYYY-MM-DD` value for a date, or the empty string, which is how a control says nothing. */
 export declare const dateAsValue: (date: Date | null) => string;
 /**

package/dist/utils/value-as/value-as.js

@@ -11,6 +11,7 @@ export const valueAsDate = (value) => {
     const rolled = date.getUTCFullYear() !== year || date.getUTCMonth() !== month - 1 || date.getUTCDate() !== day;
     return rolled ? null : date;
 };
+export const isDateValue = (value) => valueAsDate(value) !== null;
 export const dateAsValue = (date) => {
     if (!date || Number.isNaN(date.getTime())) {
         return '';

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@fusion.dev/helix-core",
   "description": "Helix element primitives: base classes, mixins, decorators, utilities.",
-  "version": "0.58.0",
+  "version": "0.58.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.58.0"
+    "@fusion.dev/helix-icons": "0.58.1"
   },
   "devDependencies": {
     "@custom-elements-manifest/analyzer": "^0.11.0",
-    "@fusion.dev/helix-cem": "0.58.0",
-    "@fusion.dev/helix-testing": "0.58.0",
+    "@fusion.dev/helix-cem": "0.58.1",
+    "@fusion.dev/helix-testing": "0.58.1",
     "lit": "^3.2.1"
   },
   "homepage": "https://fusion.dev",