@object-ui/core 17.6.0 → 17.7.0

package/dist/evaluator/unevaluablePredicate.d.ts

@@ -0,0 +1,57 @@
+/**
+ * ObjectUI
+ * Copyright (c) 2024-present ObjectStack Inc.
+ *
+ * This source code is licensed under the MIT license found in the
+ * LICENSE file in the root directory of this source tree.
+ */
+/**
+ * Is this value a gate the author DECLARED but the client cannot EVALUATE?
+ * (objectui#11358)
+ *
+ * A predicate gate (`visible` / `hidden` / `enabled` / `disabled` /
+ * `condition`) is in one of three states, and this is the one place the third
+ * is told apart from the other two:
+ *
+ *   - **absent** — `null` / `undefined` / `''` / blank predicate text. Nothing
+ *     was declared; {@link hasDeclaredPredicate} answers "not declared" (and
+ *     reports a blank one, objectui#8069).
+ *   - **evaluable** — a boolean, a predicate string, or an envelope whose
+ *     `source` is a non-blank string.
+ *   - **declared but not evaluable** — anything else that is present: an
+ *     envelope with no string `source` (the `ast`-only `{ dialect: 'cel', ast }`
+ *     an authoring door can admit), a number (`0`, `42`), an object with no
+ *     `source` (`{}`), an array. This function answers `true` for exactly
+ *     these.
+ *
+ * Triage's ruling on objectui#11358 makes the third state "declared and
+ * faulting": it is a gate, so it is never "no gate", and it cannot be
+ * evaluated, so it takes the path every other faulting predicate takes —
+ * reported, and answered with the fail direction its key already has. Before
+ * that ruling the normalizer folded it to `undefined`, the same answer as
+ * "absent", so every reader showed / enabled / ran it in silence: ADR-0137 D4's
+ * "a gate predicate that is blank or faulting is diagnosed, never a silent
+ * `true`", broken by a fold.
+ *
+ * Read by the normalizer ({@link toPredicateInput}, which now keeps the state
+ * instead of folding it), the evaluation step
+ * (`ExpressionEvaluator.evaluateCondition`, which reports it and answers it as a
+ * fault), the canonical predicate helper (`evalFieldPredicate`, which tags its
+ * reason) and the dev-mode schema validator (which still refuses it). ⛔ Not
+ * re-exported from the package entry: it is the internal definition those four
+ * share, not public API.
+ *
+ * ⚠️ No client-side reading of what an `ast` MEANT: the client evaluates
+ * `source` text only, so an `ast` with no `source` is not evaluable here,
+ * whatever it says.
+ */
+export declare function isUnevaluablePredicate(value: unknown): boolean;
+/**
+ * The `reason` reported for a gate that is declared but cannot be evaluated,
+ * tagged like an engine reason (`[parse]`, `[type]`, `[blank]`) because it
+ * travels the same two channels — `evalFieldPredicate`'s one-time warning and
+ * its `onFault` passback — and a caller that routes on the tag must tell it
+ * apart from a predicate that faulted with text in it: the fix is to give the
+ * gate a `source` (or delete it), never to debug CEL syntax.
+ */
+export declare const UNEVALUABLE_PREDICATE_REASON: string;

package/dist/evaluator/unevaluablePredicate.js

@@ -0,0 +1,70 @@
+/**
+ * ObjectUI
+ * Copyright (c) 2024-present ObjectStack Inc.
+ *
+ * This source code is licensed under the MIT license found in the
+ * LICENSE file in the root directory of this source tree.
+ */
+/**
+ * Is this value a gate the author DECLARED but the client cannot EVALUATE?
+ * (objectui#11358)
+ *
+ * A predicate gate (`visible` / `hidden` / `enabled` / `disabled` /
+ * `condition`) is in one of three states, and this is the one place the third
+ * is told apart from the other two:
+ *
+ *   - **absent** — `null` / `undefined` / `''` / blank predicate text. Nothing
+ *     was declared; {@link hasDeclaredPredicate} answers "not declared" (and
+ *     reports a blank one, objectui#8069).
+ *   - **evaluable** — a boolean, a predicate string, or an envelope whose
+ *     `source` is a non-blank string.
+ *   - **declared but not evaluable** — anything else that is present: an
+ *     envelope with no string `source` (the `ast`-only `{ dialect: 'cel', ast }`
+ *     an authoring door can admit), a number (`0`, `42`), an object with no
+ *     `source` (`{}`), an array. This function answers `true` for exactly
+ *     these.
+ *
+ * Triage's ruling on objectui#11358 makes the third state "declared and
+ * faulting": it is a gate, so it is never "no gate", and it cannot be
+ * evaluated, so it takes the path every other faulting predicate takes —
+ * reported, and answered with the fail direction its key already has. Before
+ * that ruling the normalizer folded it to `undefined`, the same answer as
+ * "absent", so every reader showed / enabled / ran it in silence: ADR-0137 D4's
+ * "a gate predicate that is blank or faulting is diagnosed, never a silent
+ * `true`", broken by a fold.
+ *
+ * Read by the normalizer ({@link toPredicateInput}, which now keeps the state
+ * instead of folding it), the evaluation step
+ * (`ExpressionEvaluator.evaluateCondition`, which reports it and answers it as a
+ * fault), the canonical predicate helper (`evalFieldPredicate`, which tags its
+ * reason) and the dev-mode schema validator (which still refuses it). ⛔ Not
+ * re-exported from the package entry: it is the internal definition those four
+ * share, not public API.
+ *
+ * ⚠️ No client-side reading of what an `ast` MEANT: the client evaluates
+ * `source` text only, so an `ast` with no `source` is not evaluable here,
+ * whatever it says.
+ */
+export function isUnevaluablePredicate(value) {
+    if (value === null || value === undefined)
+        return false;
+    if (typeof value === 'boolean' || typeof value === 'string')
+        return false;
+    if (typeof value === 'object') {
+        return typeof value.source !== 'string';
+    }
+    // A number (`0` included — it is present, not absent), a function, a symbol
+    // or a bigint: nothing a predicate is spelled as.
+    return true;
+}
+/**
+ * The `reason` reported for a gate that is declared but cannot be evaluated,
+ * tagged like an engine reason (`[parse]`, `[type]`, `[blank]`) because it
+ * travels the same two channels — `evalFieldPredicate`'s one-time warning and
+ * its `onFault` passback — and a caller that routes on the tag must tell it
+ * apart from a predicate that faulted with text in it: the fix is to give the
+ * gate a `source` (or delete it), never to debug CEL syntax.
+ */
+export const UNEVALUABLE_PREDICATE_REASON = '[unevaluable] the gate is declared but has no `source` to evaluate (an ' +
+    '`ast`-only envelope, a number, an object or an array) — it fails in the ' +
+    'direction its key fails on any fault';

package/dist/index.d.ts

@@ -8,6 +8,7 @@
 export type { SchemaNode, ComponentRendererProps } from './types/index.js';
 export * from './registry/Registry.js';
 export * from './registry/public-blocks.js';
+export * from './registry/html-tier-intrinsics.js';
 export * from './registry/PluginSystem.js';
 export * from './registry/PluginScopeImpl.js';
 export * from './registry/WidgetRegistry.js';
@@ -17,9 +18,12 @@ export * from './utils/dom-props.js';
 export * from './utils/filter-converter.js';
 export * from './utils/managedBy.js';
 export * from './utils/extract-records.js';
+export * from './utils/non-grid-row-ceiling.js';
+export * from './utils/emptiness.js';
 export * from './utils/expand-fields.js';
 export * from './utils/retired-field-types.js';
 export * from './utils/unmaterialized-fields.js';
+export * from './utils/column-sortability.js';
 export * from './utils/column-identity.js';
 export * from './utils/sort-values.js';
 export * from './utils/sort-query.js';
@@ -51,14 +55,24 @@ export * from './utils/dashboard-filters.js';
 export * from './utils/merge-filters.js';
 export * from './utils/compare-to.js';
 export * from './utils/chart-series.js';
+export * from './utils/chart-measure-key.js';
+export * from './utils/chart-category-key.js';
+export * from './utils/object-aggregate-query.js';
 export * from './utils/chart-presentation.js';
 export * from './utils/number-display.js';
+export * from './utils/date-display.js';
+export * from './utils/native-date-value.js';
 export * from './utils/dataset-format.js';
 export * from './utils/dataset-pivot.js';
 export * from './utils/record-title.js';
+export * from './utils/record-color.js';
 export * from './utils/export-filename.js';
 export * from './utils/reference-keys.js';
 export * from './utils/predicate-record.js';
+export * from './utils/without-denied-fields.js';
+export * from './utils/parent-scope.js';
 export * from './utils/predicate-fields.js';
+export * from './utils/grouping-fields.js';
 export * from './utils/normalize-list-view.js';
+export * from './utils/record-source.js';
 export * from './utils/humanize-label.js';

package/dist/index.js

@@ -7,6 +7,7 @@
  */
 export * from './registry/Registry.js';
 export * from './registry/public-blocks.js';
+export * from './registry/html-tier-intrinsics.js';
 export * from './registry/PluginSystem.js';
 export * from './registry/PluginScopeImpl.js';
 export * from './registry/WidgetRegistry.js';
@@ -21,6 +22,17 @@ export * from './utils/dom-props.js';
 export * from './utils/filter-converter.js';
 export * from './utils/managedBy.js';
 export * from './utils/extract-records.js';
+// The non-grid row ceiling (objectui#7210), homed beside the `extractRecords`
+// it wraps by objectui#7508's ruling A′. `@object-ui/react` re-exports three of
+// these names and keeps only the React footnote, `NonGridRowCeilingNote`.
+export * from './utils/non-grid-row-ceiling.js';
+// The emptiness FLOOR (objectui#8496, director seat, decision batch #86): the
+// weakest common claim about "is this value empty" — `null`, `undefined`, the
+// empty string, the empty array — below `plugin-detail`, `plugin-list`,
+// `plugin-kanban` and `@object-ui/fields`, each of which used to spell those
+// four members privately. Surfaces EXTEND it or DECLINE a member out loud; ⛔
+// the floor itself never grows past the four.
+export * from './utils/emptiness.js';
 export * from './utils/expand-fields.js';
 // The RETIREMENT gate (objectui#4914, maintainer ruling B). Homed here rather
 // than in `@object-ui/fields` because `@object-ui/components` is one of its six
@@ -29,6 +41,12 @@ export * from './utils/expand-fields.js';
 // name, so its published surface is unchanged.
 export * from './utils/retired-field-types.js';
 export * from './utils/unmaterialized-fields.js';
+// [#5729] The consumer half of objectstack#10235's ruling: the SERVED
+// per-column sortability projection, and the one spelling of its contract
+// (`entry exists && sortable: true`). Homed beside the storage-fact set above
+// because a consumer that reaches for one must be able to see the other and
+// know which one the platform actually served.
+export * from './utils/column-sortability.js';
 export * from './utils/column-identity.js';
 export * from './utils/sort-values.js';
 export * from './utils/sort-query.js';
@@ -55,14 +73,29 @@ export * from './runtime/capabilities.js';
 export { composeStacks } from '@objectstack/spec';
 export * from './utils/drill-down.js';
 export * from './utils/date-macros.js';
-// Session-scoped filter placeholders ({current_user_id} / {current_org_id})
+// Session-scoped filter placeholders ({current_user_id} / {current_org_id}),
+// the record-scoped `{record_id}` (objectui#7297),
 // plus `resolveFilterPlaceholders`, the single entry point every surface
-// should call so no vocabulary is silently skipped (framework #3574).
+// should call so no vocabulary is silently skipped (objectstack-ai/objectstack#3574).
 export * from './utils/filter-tokens.js';
 export * from './utils/dashboard-filters.js';
 export * from './utils/merge-filters.js';
 export * from './utils/compare-to.js';
 export * from './utils/chart-series.js';
+// "Which result column carries the measure?" — one answer for the row
+// projection and the series binding alike, delegated to the spec's own
+// derivation so the two cannot drift (objectui#8266).
+export * from './utils/chart-measure-key.js';
+// "Which result column carries the CATEGORY?" — the same move on the other
+// axis, delegated to the contract's own published derivation so a relay cannot
+// floor the x-axis binding on a literal the aggregate contradicts
+// (objectui#8269).
+export * from './utils/chart-category-key.js';
+// "Which CALL does an object-bound aggregate make when its `groupBy` is the
+// structured date-bucketing node?" — the same move on the REQUEST rather than
+// on a result column, so the chart and the metric cannot post two different
+// wires for one authored shape (objectui#8613).
+export * from './utils/object-aggregate-query.js';
 // The AUTHORED half of a dataset-bound chart (objectui#4229's data/presentation
 // split), shared by the dashboard widget and the report's embedded chart so the
 // same spec keys are lowered identically on both (objectui#4877).
@@ -73,12 +106,26 @@ export * from './utils/chart-presentation.js';
 // `dataset-format` below from reaching it (so the two drifted). `@object-ui/i18n`
 // re-exports these names unchanged, so both import paths name the same symbol.
 export * from './utils/number-display.js';
+// The ONE date-display path (objectui#7178) — the same story one type over.
+// It lived in `@object-ui/fields`' React barrel, which `dataset-format`
+// below could not import, so a date-valued measure rendered its raw ISO
+// string. `@object-ui/fields` re-exports these names unchanged.
+export * from './utils/date-display.js';
+// The native date/time control adapters (objectui#3127), moved down from
+// `@object-ui/fields` so `@object-ui/components`' data table can share them
+// instead of keeping private copies (objectui#10625). `@object-ui/fields`
+// re-exports these names unchanged.
+export * from './utils/native-date-value.js';
 export * from './utils/dataset-format.js';
 // Pivot lookup-key encoders, shared by every cross-tab renderer so the
 // dashboard widget and the report renderer key their buckets identically
 // (objectstack#5473 / objectstack#5665).
 export * from './utils/dataset-pivot.js';
 export * from './utils/record-title.js';
+// The one `colorField` ladder every record view shares (objectui#7243) — the
+// gantt, calendar and timeline all resolve an authored option colour here
+// instead of each guessing at the raw stored value.
+export * from './utils/record-color.js';
 export * from './utils/export-filename.js';
 export * from './utils/reference-keys.js';
 // Binds a fetched record into an expression scope the way the SERVER binds it
@@ -86,10 +133,41 @@ export * from './utils/reference-keys.js';
 // `toPredicateRecord` for why an unnormalized one gives the same predicate
 // different verdicts on different surfaces.
 export * from './utils/predicate-record.js';
+// The field-read rule for ONE record (objectui#10594, ruling A): the row as the
+// viewer may read it, which every surface that builds a display value from a
+// whole row calls. It replaced module-private copies in `@object-ui/fields`,
+// `@object-ui/react`, `@object-ui/app-shell` and `@object-ui/plugin-detail`.
+export * from './utils/without-denied-fields.js';
+// The parent-relationship condition a detail-page related list is scoped by.
+// One implementation, imported by BOTH the row query and the tab-badge count
+// probe — objectui#8882 is what two of them cost.
+export * from './utils/parent-scope.js';
 // The other half of a view's field appetite: the fields its PREDICATES read,
 // which the column-derived `$select` never asked the server for.
 export * from './utils/predicate-fields.js';
+// The THIRD source of a view's field appetite: the fields it GROUPS BY. The
+// spec's `grouping` block is a sibling of `columns`, not a subset, so a grid
+// may group by a field it never shows (objectui#7179).
+export * from './utils/grouping-fields.js';
 export * from './utils/normalize-list-view.js';
+// The ONE record-source ladder, both halves. `resolveRecordSourceConfig`
+// (`ce2aaefe1`) is the PRODUCER — the ruled `data` / `staticData` /
+// `objectName` ladder, hand-copied into five view plugins with no gate holding
+// them together. `resolveRecordSourceObjectName` (`b041b9c0c`) is the READER
+// over its output: six view plugins each spelled "the object this block is
+// bound to — the resolved data config's object when it names one, else
+// `objectName`" locally, and had drifted. Both are deliberately SEPARATE from
+// the `normalizeListViewSchema` gap-fill above: that one answers how
+// `objectName` gets POPULATED when absent (#7477 ruling B), these answer which
+// object a block RESOLVES (the three-rung ladder `77cb489b4` declared). Merging them
+// would override one standing ruling or the other.
+// A THIRD reading ships beside them since objectui#9571:
+// `recordSourceDataArmForType` answers which `data` arm a registered block TYPE
+// declares, for the one consumer that cannot be handed the arm as a parameter —
+// `SchemaRenderer`, which is generic over every type and holds only
+// `schema.type`. Read its docblock before adding a row; it transports the call
+// sites' own literals rather than re-deriving them.
+export * from './utils/record-source.js';
 // The single home for the VALUE fallback prettifier (a stored value becomes a
 // display string when nothing resolves it). `@object-ui/fields` and
 // `@object-ui/plugin-charts` each carried a byte-identical private copy;

package/dist/protocols/index.d.ts

@@ -7,5 +7,4 @@
  */
 export * from './DndProtocol.js';
 export * from './KeyboardProtocol.js';
-export * from './ResponsiveProtocol.js';
 export * from './SharingProtocol.js';

package/dist/protocols/index.js

@@ -15,5 +15,13 @@ export * from './KeyboardProtocol.js';
 // which declares its own `NotificationSystemConfig` and is what every surface
 // reads. Re-typing the bridge would have meant re-declaring a vocabulary the
 // spec had just retired (AGENTS.md #0.1).
-export * from './ResponsiveProtocol.js';
+// `ResponsiveProtocol` removed in the objectstack#11027 uptake (objectui#7580):
+// it bridged `@objectstack/spec/ui`'s `ResponsiveConfig`, which that retirement
+// deleted with no successor, and it had zero importers in this repo (measured on
+// objectui#4773; `docs/audits/2901-spec-enum-renderer-coverage.md` had already
+// recorded it as one of the zero-importer protocols). Re-typing the bridge would
+// have meant re-declaring a vocabulary the spec had just retired, for a reader
+// that does not exist — AGENTS.md #0.1, and the same disposition
+// `NotificationProtocol` got above. The layout vocabulary that DOES have a
+// renderer is re-homed instead, in `@object-ui/types` and `@object-ui/layout`.
 export * from './SharingProtocol.js';