@svgrid/enterprise 2.6.0 → 2.6.1

package/dist/schema.d.ts

@@ -268,6 +268,19 @@ export type FormSection = {
     fields: string[];
     /** Show the section only while this holds - see `EntityField.when`. */
     visibleWhen?: PredicateExpr;
+    /**
+     * Let the user fold this group away. Turns the heading into a disclosure
+     * button, so a long form opens at a readable length instead of a wall of
+     * inputs.
+     *
+     * A collapsed section is still **filled in and still validated** - it is a
+     * display state, not a condition. Use `visibleWhen` to actually drop fields
+     * from the form. If a collapsed section holds an error the panel opens it, so
+     * a failed submit can never point at something the user cannot see.
+     */
+    collapsible?: boolean;
+    /** Start folded. Only meaningful with `collapsible`. */
+    collapsed?: boolean;
 };
 /**
  * How the entity's form is laid out. Lives on the schema rather than on the
@@ -281,6 +294,25 @@ export type FormSection = {
 export type FormLayout = {
     columns?: 1 | 2 | 3;
     sections?: FormSection[];
+    /**
+     * Ask one section at a time, with Back / Next and a progress line - an intake
+     * form or an onboarding flow rather than a page of inputs.
+     *
+     * Each section is a step, so the sections ARE the design: no second list to
+     * keep in sync. **Next validates only the step you are on**, so a long form
+     * fails early and locally instead of dumping every error at the end. A section
+     * hidden by `visibleWhen` is skipped rather than shown empty, so the step count
+     * follows the answers.
+     *
+     * Needs sections (with none, it is one page and this does nothing) and makes
+     * `collapsible` moot - a step is already one group at a time.
+     *
+     * A server-rendered screen renders the steps as ordinary sections: stepping
+     * through a `<form>` with no JavaScript would mean a round-trip per step and
+     * somewhere to keep the half-finished record. The server still validates
+     * everything either way.
+     */
+    steps?: boolean;
 };
 /** Normalized descriptor the edit panel renders from (one per visible-in-form field). */
 export type FormFieldDescriptor = {
@@ -325,6 +357,13 @@ export declare function titleCase(field: string): string;
  * `getRowId`, edit panel, adapters) needs a stable key.
  */
 export declare function resolveIdField<TData extends RowData>(schema: EntitySchema<TData>): string;
+/**
+ * Whether a field is hidden from one surface. Public because the `hidden`
+ * union (`true` means both surfaces, an object names them) is exactly the kind
+ * of logic that drifts when every caller re-derives it - the form builder's
+ * "Hidden from this form" tray is one such caller.
+ */
+export declare function isFieldHidden(field: Pick<EntityField, 'hidden'>, surface: 'grid' | 'form'): boolean;
 /**
  * Derive grid columns from a schema. Read-only fields become non-editable
  * columns; `enum` carries its options through as `editorOptions`. The

package/dist/schema.js

@@ -75,6 +75,15 @@ function hiddenFor(field, surface) {
         return field.hidden[surface] === true;
     return false;
 }
+/**
+ * Whether a field is hidden from one surface. Public because the `hidden`
+ * union (`true` means both surfaces, an object names them) is exactly the kind
+ * of logic that drifts when every caller re-derives it - the form builder's
+ * "Hidden from this form" tray is one such caller.
+ */
+export function isFieldHidden(field, surface) {
+    return hiddenFor(field, surface);
+}
 /**
  * Derive grid columns from a schema. Read-only fields become non-editable
  * columns; `enum` carries its options through as `editorOptions`. The