@uniweb/core 0.36.0 → 0.37.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uniweb/core",
-  "version": "0.36.0",
+  "version": "0.37.0",
   "description": "Core classes for the Uniweb platform - Uniweb, Website, Page, Block",
   "type": "module",
   "exports": {

package/src/index.js

@@ -93,7 +93,10 @@ export {
   landingRoute,
   RESOLUTION_STATUS,
 } from './resolve-route.js'
-export { isRichSchema } from './schemas.js'
+// ⛔ No `isRichSchema` (removed 2026-10-05). It told a form-shaped `data:` value from a field
+// map for the runtime's field defaults and the build's runtime schema; both went when the
+// runtime stopped filling field defaults. A registered schema says it outright — `kind: 'form'`
+// in format 3 (`@uniweb/schemas/foundation`) — and the editor, its last reader, reads that.
 // ⛔ `Tracker` is NOT on the package entry. It is a FEATURE, not part of the
 // object graph this package exists to define, and putting it here made every
 // consumer of core carry 1,576 gzip of it -- press, unipress, `@uniweb/api`

package/src/website.js

@@ -755,7 +755,7 @@ export default class Website {
   /**
    * Get layout metadata from foundation config
    * @param {string} layoutName - Layout name
-   * @returns {Object|null} Layout meta { areas, transitions, defaults }
+   * @returns {Object|null} Layout meta { transitions, layers, scroll, defaults } — a page's areas are its site's `layout/` folder (`getLayoutAreas`)
    */
   getLayoutMeta(layoutName) {
     return findLayoutEntry(globalThis.uniweb?.foundationConfig?.layoutMeta, layoutName) || null

package/src/schemas.js

@@ -1,45 +0,0 @@
-/**
- * The rich-form-schema predicate. One function, and deliberately only one.
- *
- * Rich schemas live under `data.schemas` in a component's meta.js. They drive
- * two author input paths that both land at `content.data[schema-id]`: tagged
- * markdown blocks (``` ```yaml:<id> ``` ```) and the editor's FormBlock widget.
- *
- * `isRichSchema` is a **dispatch** predicate — "is this already the rich shape?"
- * — and it is read at render by `runtime/src/prepare-props.js` (`applySchemas`)
- * and at build by `build/src/runtime-schema.js`. Both are on the hot path of
- * every site, which is what earns it a place in this package.
- *
- * ⛔ **Do not add editor-side schema code here.** `normalizeSchema` — "can this
- * be edited, and as what?" — sat beside this function until 2026-09-01 purely
- * because the two were adjacent; it never called `isRichSchema` and had no
- * consumer outside the editor. `@uniweb/core` loads on every site in every lane
- * and is not tree-shaken on the hosted one, so an editor-only function on its
- * entry is paid for by every visitor of every site. It now lives in the
- * zero-dependency leaf that owns what a data-schema *means*:
- * **`@uniweb/schemas/editor-form`**.
- *
- * Conditional field visibility (a rich-schema feature) is likewise editor-only
- * and is not implemented here — the editor owns its own evaluator.
- */
-
-/**
- * Does a `data.schemas` entry look like a rich form schema?
- *
- * Rich schemas have an ordered `fields` array (composite arrays and
- * nested objects), distinct from simple keyed-object schemas used for
- * tagged blocks. Markers (any of):
- *   - `fields` is an array
- *   - `isComposite: true`
- *   - `childSchema` present
- *
- * @param {*} schema - Schema value to inspect.
- * @returns {boolean}
- */
-export function isRichSchema(schema) {
-  if (!schema || typeof schema !== 'object') return false
-  if (Array.isArray(schema.fields)) return true
-  if (schema.isComposite === true) return true
-  if (schema.childSchema && typeof schema.childSchema === 'object') return true
-  return false
-}