TAI42 — the OS for AI tools

The schema-driven form renderer and the JSON Schema helpers it is built on.

CompletionProvider

type CompletionProvider = (argName: string, partial: string) => Promise<string[]>

Fetch argument-value suggestions for a string field. argName is the field’s path within the form (a property key at the root, a dotted path when nested); partial is the value typed so far. The caller owns the source (e.g. an MCP completion/complete call) — SchemaForm only routes string fields through the completion-backed input when a provider is supplied.

DateRangePair

interface DateRangePair

A START/END pair drawable as one range control, resolved off a page’s properties. Properties

Property	Type	Description
`endName`	`string`	—
`endSchema`	`JsonSchema`	—
`endTimeName?`	`string`	The END’s `timeOf` time property among the same properties, when it has one.
`endTimeSchema?`	`JsonSchema`	—
`startName`	`string`	—
`startSchema`	`JsonSchema`	—
`startTimeName?`	`string`	The START’s `timeOf` time property among the same properties, when it has one.
`startTimeSchema?`	`JsonSchema`	—

Related: JsonSchema

Discriminator

interface Discriminator

A Pydantic-style discriminated-union tag: which property selects the variant. Properties

Property	Type	Description
`mapping?`	`Readonly<Record<string, string>>`	—
`propertyName`	`string`	—

ExpressionFieldComponent

type ExpressionFieldComponent = ComponentType<ExpressionFieldProps>

The expression-authoring door a host INJECTS into the form — JqField, which the host imports straight from @tai42/jq-studio. It is a COMPONENT, rendered as an element, never called as a function: the door owns hooks and state (editor open, worker handle), which only survive as its own element identity. A host may inject a lazy door to keep the jq subgraph in a split chunk — the form mounts it inside a Suspense boundary that paints the resting shell while that chunk resolves. Related: ExpressionFieldProps

ExpressionFieldContext

const ExpressionFieldContext: Context<ExpressionFieldComponent | undefined>

The ambient door for the whole form. Absent (the default), an expression-annotated field renders the PLAIN string input, byte-identically to an unannotated one — the jq authoring door is opt-in, because the dynamic import that would fetch it on demand still EMITS its chunks, worker, and wasm into every consumer that bundles the SDK. A host wires it ONCE above its tree (SchemaEditor’s preview and ElicitationForm render forms a caller does not own the props of, and a plugin page renders its own); the form’s own expressionField prop overrides it for a single form. Related: ExpressionFieldComponent

ExpressionFieldProps

interface ExpressionFieldProps

Exactly the props the form hands an injected expression field — no more, so any expression editor can satisfy the contract, and no less, so the form is free to pass all of them. The label/description/error slots are the door’s own chrome: an expression field brings its a11y-linked label and helper slots, so the form does NOT wrap it in the usual Field. Properties

Property	Type	Description
`description?`	`ReactNode`	—
`error?`	`ReactNode`	—
`label`	`string`	—
`multiline?`	`boolean`	Render a multiline resting control; the form always asks for one.
`onChange`	`(value: string) => void`	—
`shape?`	`ExpressionInputShape`	—
`value`	`string`	—

Related: ExpressionInputShape

ExpressionInputKey

interface ExpressionInputKey

One top-level key of the expression’s input document, with a one-line gloss. Properties

Property	Type	Description
`gloss`	`string`	—
`name`	`string`	—

ExpressionInputShape

interface ExpressionInputShape

What . IS for an expression-annotated field, as the form hands it to the injected door. Built by the renderer from the schema’s x-tai42-expression annotation. Like the annotation type it is built from, this MIRRORS jq-studio’s input-shape descriptor without importing it: the schema-form tree names no jq type, in code OR in its declarations, which is what keeps a consumer that never injects a door free of the jq subgraph. JqField satisfies it structurally; a test pins that. Properties

Property	Type	Description
`blurb`	`string`	One sentence: what `.` is in this field.
`caveats?`	`readonly string[]`	Per-field caveats.
`id`	`string`	Stable, host-namespaced id, opaque to the door (memoisation/telemetry).
`keys`	`readonly ExpressionInputKey[]`	The top-level keys of `.`, each with a one-liner.
`label`	`string`	Short chip label — what `.` is here, e.g. “node envelope”.
`returns`	`string`	What the expression must RETURN, e.g. “true or false”.
`sample?`	`unknown`	A static skeleton of `.` for the door’s test surface.
`variables?`	`readonly ExpressionInputVariable[]`	The named variables the expression reads as `$name` beside `.`; omitted when the field declares none.

Related: ExpressionInputKey

FieldWords

interface FieldWords

A form field’s own words, keyed by the root object’s property name in a form’s fieldWording. Every member is optional; an unset one draws the SDK’s own word.

choiceLabel: the placeholder of the field’s enum select (in place of Select…).
invalid: the sentence that replaces every shape error on the field and anything inside it (a format, pattern, length, bound, type or item error).
required: the sentence shown when the field’s required value is missing, at the field or anywhere inside it (in place of "<name>" is required).
addItem / removeItem / itemLabel / noItems: a list field’s add button, each item’s remove button, each item’s heading (its {n} token takes the item’s number), and the line shown while the list is empty.

Properties

Property	Type	Description
`addItem?`	`string`	—
`choiceLabel?`	`string`	—
`invalid?`	`string`	—
`itemLabel?`	`string`	—
`noItems?`	`string`	—
`removeItem?`	`string`	—
`required?`	`string`	—

FormControl

type FormControl = "chips" | "textarea"

The CONTROL a surface draws for a property in place of the default for the property’s shape. chips draws a choice (a string with an enum, or an array of such strings) as a tap-to-select chip grid instead of the radio/select or checkbox group. textarea draws a string as a multi-line text control instead of a single-line box. It changes what is DRAWN, never what is accepted — the value and its validation stay the property’s own.

FormInputMode

type FormInputMode = "text" | "numeric" | "decimal" | "tel" | "email" | "url"

The input KIND a string field collects, drawn as the matching keyboard or native control. The vocabulary is the HTML inputmode/control naming of the concept: numeric/decimal set a text box’s keyboard hint; tel/email/url select the matching native control. It draws, it does not validate.

JsonSchema

interface JsonSchema

A structural JSON Schema node. All keys optional; the index signature keeps the type permissive so an unrecognized keyword is never a type error — it is a runtime classification concern the renderer handles. Properties

Property	Type	Description
`$defs?`	`Readonly<Record<string, JsonSchema>>`	—
`$ref?`	`string`	—
`additionalProperties?`	`boolean \| JsonSchema`	—
`allOf?`	`readonly JsonSchema[]`	—
`anyOf?`	`readonly JsonSchema[]`	—
`const?`	`unknown`	—
`contentEncoding?`	`string`	Media annotations (see the `SchemaForm` module). `contentEncoding: "base64"` together with `contentMediaType` (or `format: "data-url"`) opts a string field into the upload control; `contentMaxBytes` pins a per-field size cap. `contentMaxBytes` is a NONSTANDARD JSON-Schema extension keyword — a standard JSON-Schema validator ignores it. The client-side caps it drives (see the `media` module) are UX guards, NOT a security boundary: the SERVER MUST independently validate the decoded size of any uploaded content.
`contentMaxBytes?`	`number`	—
`contentMediaType?`	`string`	—
`control?`	`FormControl`	The CONTROL to draw for this property in place of its shape’s default — a platform keyword (see FormControl). `chips` draws a `string`-with-`enum` or an `array` of such strings as a chip grid; `textarea` draws a `string` as a multi-line text control. It DRAWS, it does not validate — the answer door still enforces the property’s `type`, `enum`, `maxLength` and the rest. A value outside the set is read as absent (the server ask door is the authority that refuses it).
`default?`	`unknown`	—
`definitions?`	`Readonly<Record<string, JsonSchema>>`	—
`description?`	`string`	—
`discriminator?`	`Discriminator`	—
`enum?`	`readonly unknown[]`	—
`format?`	`string`	—
`inputMode?`	`FormInputMode`	The input KIND a `string` field collects — a platform keyword (see FormInputMode). The renderer draws the matching keyboard or native control: `numeric`/`decimal` a text box with that keyboard hint (the value stays the typed string, so `"007"` keeps its leading zeros), `tel`/`email`/`url` the matching native control, `text` or absent a plain text box. It DRAWS, it does not validate — the answer door still enforces `type`, `pattern` and `format`. When present it OUTRANKS `format` for the control. A value outside the set is read as absent (the server ask door is the authority that refuses it).
`items?`	`JsonSchema`	—
`maxDate?`	`string`	—
`maxDays?`	`number`	—
`maxItems?`	`number`	—
`maxLength?`	`number`	—
`maximum?`	`number`	—
`minDate?`	`string`	Platform date-constraint keys on a `string`/`date` (or `date-time`) property. They are NOT the JSON-Schema numeric keywords (which are inert on a string): `minDate`/ `maxDate` are inclusive `YYYY-MM-DD` bounds, `unavailableDates` is a list of `YYYY-MM-DD` days to exclude. A date RANGE is TWO ordinary date fields: the END field names its start field with `rangeStart` and carries the inclusive span in `minDays`/`maxDays`; nothing is recombined. All optional; absent = an unconstrained date. The native control enforces what it can (min/max) and the validator enforces the rest, mirroring the server.
`minDays?`	`number`	—
`minItems?`	`number`	—
`minLength?`	`number`	—
`minimum?`	`number`	—
`oneOf?`	`readonly JsonSchema[]`	—
`pattern?`	`string`	—
`properties?`	`Readonly<Record<string, JsonSchema>>`	—
`rangeStart?`	`string`	—
`required?`	`readonly string[]`	—
`timeOf?`	`string`	On a `string`/`format: time` property: the name of the range-end `date` property this is the time of. The time draws right after its date (inside the range group when the pair merges), and two ends on the same date are then ordered by their times. Absent = a time field of its own.
`title?`	`string`	—
`type?`	`JsonSchemaType \| readonly JsonSchemaType[]`	—
`unavailableDates?`	`readonly string[]`	—
`visibleWhen?`	`VisibleWhen`	A declarative visibility predicate on a property: the field shows only when the predicate holds against the current form values. Static form description evaluated by the renderer (never a consumer reaction); a hidden field is not rendered and not validated. Absent = always visible. See VisibleWhen.

JsonSchemaType

type JsonSchemaType = "string" | "number" | "integer" | "boolean" | "object" | "array" | "null"

The JSON-Schema type keyword values Pydantic emits.

NoFiniteValueError

NoFiniteValueError

Thrown by defaultValueForSchema and skeletonValueForSchema when the schema admits no finite value: a chain of required properties refers back to its own definition with no null accepted on the way. A caller that seeds on a user action catches exactly this type to show the failure on its field; any other error is not a seeding outcome and propagates.

RecordEntryContext

interface RecordEntryContext

One record entry, handed to a host-supplied value renderer. Properties

Property	Type	Description
`defaultField`	`ReactNode`	The default value editor the record field would render for this entry.
`keyName`	`string`	The entry’s current key (may be blank/duplicate while the user edits).
`onChange`	`(value: unknown) => void`	—
`path`	`string`	The entry value’s form path (dotted from the form root).
`value`	`unknown`	—
`valueSchema`	`JsonSchema`	The entry value schema, as written (the renderer resolves any `$ref`).

Related: JsonSchema

RecordEntryRenderer

type RecordEntryRenderer = (entry: RecordEntryContext) => ReactNode

A host-supplied per-entry value renderer for record fields — the injection point a masked/secret editor (or any other value affordance) mounts through. It returns the node to render in the entry’s value slot; returning entry.defaultField falls back to the built-in editor. Absent (the default), every entry renders its defaultField. Related: RecordEntryContext

RecordEntryRendererContext

const RecordEntryRendererContext: Context<RecordEntryRenderer | undefined>

Related: RecordEntryRenderer

SchemaForm

function SchemaForm(props: SchemaFormProps): ReactNode

Render a controlled form for schema. The root is usually an object (a tool’s input schema); a scalar/array/union root renders as a single field group. Props

Prop	Type	Description
`completionProvider?`	`CompletionProvider`	Optional. When supplied, every string field renders through the completion-backed input (argument autocomplete); when omitted, string fields render as a plain text input — the default, unchanged behaviour.
`errors?`	`Readonly<Record<string, string>>`	—
`expressionField?`	`ExpressionFieldComponent`	Optional. The expression-authoring door for `x-tai42-expression` fields — `JqField` from `@tai42/jq-studio`, which the host imports directly and passes here (see the module doc-comment). Omitted, the enclosing ExpressionFieldContext supplies it; absent both, an annotated field renders the plain string input.
`fieldWording?`	`Readonly<Record<string, FieldWords>>`	Optional. Per-field words, keyed by the root object’s property name. A top-level `enum` field that draws as a select shows its entry’s `choiceLabel` as the select placeholder (in place of the default `Select…`); a top-level list field draws its entry’s `addItem`, `removeItem`, `itemLabel` (`{n}` the item’s number) and `noItems` (in place of `Add item`, `Remove`, `Item {n}` and `No items`). Nested fields and other controls are unaffected, and a field with no entry draws the defaults. The entry’s `invalid` and `required` sentences are not read here: pass the same record to `validateAgainstSchema` as `fieldWording`, and the errors it returns carry them.
`idPrefix?`	`string`	—
`maxUploadBytes?`	`number`	Optional. Default byte cap for media-upload fields (see the module doc-comment). A field’s own `contentMaxBytes` annotation overrides it; absent both, DEFAULT_MAX_UPLOAD_BYTES applies.
`onChange`	`(value: unknown) => void`	—
`schema`	`JsonSchema`	—
`value`	`unknown`	—

Related: SchemaFormProps

SchemaFormErrors

type SchemaFormErrors = Readonly<Record<string, string>>

A structured, per-path bag of validation problems. Keys are dotted/bracketed paths from the form root ("" = the root value, "user.name", "tags[0]"); each entry is a loud, human-readable message. Empty object = valid.

SchemaFormProps

interface SchemaFormProps

Properties

Property	Type	Description
`completionProvider?`	`CompletionProvider`	Optional. When supplied, every string field renders through the completion-backed input (argument autocomplete); when omitted, string fields render as a plain text input — the default, unchanged behaviour.
`errors?`	`Readonly<Record<string, string>>`	—
`expressionField?`	`ExpressionFieldComponent`	Optional. The expression-authoring door for `x-tai42-expression` fields — `JqField` from `@tai42/jq-studio`, which the host imports directly and passes here (see the module doc-comment). Omitted, the enclosing ExpressionFieldContext supplies it; absent both, an annotated field renders the plain string input.
`fieldWording?`	`Readonly<Record<string, FieldWords>>`	Optional. Per-field words, keyed by the root object’s property name. A top-level `enum` field that draws as a select shows its entry’s `choiceLabel` as the select placeholder (in place of the default `Select…`); a top-level list field draws its entry’s `addItem`, `removeItem`, `itemLabel` (`{n}` the item’s number) and `noItems` (in place of `Add item`, `Remove`, `Item {n}` and `No items`). Nested fields and other controls are unaffected, and a field with no entry draws the defaults. The entry’s `invalid` and `required` sentences are not read here: pass the same record to `validateAgainstSchema` as `fieldWording`, and the errors it returns carry them.
`idPrefix?`	`string`	—
`maxUploadBytes?`	`number`	Optional. Default byte cap for media-upload fields (see the module doc-comment). A field’s own `contentMaxBytes` annotation overrides it; absent both, DEFAULT_MAX_UPLOAD_BYTES applies.
`onChange`	`(value: unknown) => void`	—
`schema`	`JsonSchema`	—
`value`	`unknown`	—

SecretRef

type SecretRef = { key: string; source: "key" } | { secret: string; source: "paste" }

The value SecretRefField emits and reads back. The source discriminant is what the host branches on:

key — reference an existing env key; the host resolves the reference.
paste — a new plaintext secret; the host stores it under a generated key and records the reference. secret is write-only and never rendered.

SecretRefField

function SecretRefField(props: SecretRefFieldProps): ReactNode

Props

Prop	Type	Description
`availableKeys`	`readonly string[]`	Env key NAMES the host supplies (e.g. envConfig.secret_keys). Never fetched here.
`idPrefix?`	`string`	—
`initialMode?`	`"key" \| "paste"`	Which editor a value-less field opens on when key picking is available. Defaults to `'paste'` (the write-first behaviour): a host adding a brand-new secret lands on the paste input. A host that only ever REFERENCES existing keys passes `'key'` so a fresh field opens straight on the key picker rather than a paste input it would block. Has no effect once a value is committed (the chip is shown) or when key picking is off (paste-only, fail closed).
`keyPickingAvailable?`	`boolean`	Whether env-key picking is available at all — the host passes it from whether the projection carries the env route. Omitted or false: paste-only (fail closed).
`label?`	`string`	Visible field label; the accessible name of the inner control.
`onChange`	`(value: SecretRef) => void`	Fired once when a value is provided (a key picked, or a paste committed).
`pasteDisabledReason?`	`string`	When set, PASTING a new secret is blocked and this reason is surfaced inline (referencing an existing key stays available). The host passes it when a paste right now would land in the wrong place — an unsaved structural edit has shifted the target pointer, or the entry has no key yet to hint the generated name.
`value`	`SecretRef \| undefined`	The current value, or `undefined` when nothing has been provided yet.

Related: SecretRefFieldProps

SecretRefFieldProps

interface SecretRefFieldProps

Properties

Property	Type	Description
`availableKeys`	`readonly string[]`	Env key NAMES the host supplies (e.g. envConfig.secret_keys). Never fetched here.
`idPrefix?`	`string`	—
`initialMode?`	`"key" \| "paste"`	Which editor a value-less field opens on when key picking is available. Defaults to `'paste'` (the write-first behaviour): a host adding a brand-new secret lands on the paste input. A host that only ever REFERENCES existing keys passes `'key'` so a fresh field opens straight on the key picker rather than a paste input it would block. Has no effect once a value is committed (the chip is shown) or when key picking is off (paste-only, fail closed).
`keyPickingAvailable?`	`boolean`	Whether env-key picking is available at all — the host passes it from whether the projection carries the env route. Omitted or false: paste-only (fail closed).
`label?`	`string`	Visible field label; the accessible name of the inner control.
`onChange`	`(value: SecretRef) => void`	Fired once when a value is provided (a key picked, or a paste committed).
`pasteDisabledReason?`	`string`	When set, PASTING a new secret is blocked and this reason is surfaced inline (referencing an existing key stays available). The host passes it when a paste right now would land in the wrong place — an unsaved structural edit has shifted the target pointer, or the entry has no key yet to hint the generated name.
`value`	`SecretRef \| undefined`	The current value, or `undefined` when nothing has been provided yet.

Related: SecretRef

TemplatedTextCatalogContext

const TemplatedTextCatalogContext: Context<UseTemplatedTextCatalog>

The ambient stored-template source for the whole form. Absent (the default), a templated-text field gets no catalog, as every TemplatedTextField given none: the stored source offers no templates and inline content is authored as usual. Related: UseTemplatedTextCatalog

UseTemplatedTextCatalog

type UseTemplatedTextCatalog = () => TemplatedTextCatalog | undefined

The hook a host supplies so a form’s templated-text fields can offer stored templates: it returns the catalog (the template ids plus the storage-presence and fetch state) the field’s stored-template picker reads. The form holds no data edge, so the host owns the fetch; a field calls the hook only when it renders, so a form without a templated-text field never fetches the catalog. It is a HOOK, called on every render of a templated-text field, so the injected reference must be stable (a module-level function). Related: TemplatedTextCatalog

dateRangePairs

function dateRangePairs(
  properties: readonly readonly [string, JsonSchema][],
): readonly DateRangePair[]

The date-range pairs among properties that are drawable as ONE control. A pair qualifies when: the END names an existing sibling START in rangeStart; BOTH are format: date; both carry the SAME visibleWhen (deep-equal, or both absent); AND no OTHER field’s visibleWhen names either end — otherwise merging the pair would leave that field’s predicate pointing at a control that no longer draws on its own, so the pair stays two date fields (the documented degrade). properties is ONE page’s ordered list; a field is used in at most one pair. Each pair also names each end’s timeOf time among the same properties, which draws inside the group. Parameters

Parameter	Type	Default	Description
`properties`	`readonly readonly [string, JsonSchema][]`	—	—

Related: DateRangePair, JsonSchema

defaultValueForSchema

function defaultValueForSchema(schema: JsonSchema, root: JsonSchema): unknown

The initial value for a schema. root carries the $defs document for $ref resolution and defaults to the schema itself (the common whole-tool-schema call). Parameters

Parameter	Type	Default	Description
`schema`	`JsonSchema`	—	—
`root`	`JsonSchema`	`schema`	—

Related: JsonSchema

fieldDrawingOrder

function fieldDrawingOrder(
  names: readonly string[],
  properties: Readonly<Record<string, JsonSchema>>,
): string[]

names in drawing order: each timeOf time moved to sit right after the date it names. names is one page’s fields, or every property of a page-less form or a readback, in their given order. A time moves only when the name it points at is in names and does not itself point at another listed name; any other time (its date not listed, a chain of times, a cycle) keeps its place. Every name appears exactly once and every other name keeps its relative order. Pure and idempotent, so every walker that orders the same list draws it the same way. Parameters

Parameter	Type	Default	Description
`names`	`readonly string[]`	—	—
`properties`	`Readonly<Record<string, JsonSchema>>`	—	—

Related: JsonSchema

isFieldVisible

function isFieldVisible(schema: JsonSchema, values: Record<string, unknown>): boolean

Whether a property carrying schema.visibleWhen is visible against the current values of its enclosing object. Absent predicate ⇒ always visible. Exactly one of equals/in/notEmpty must be present; otherwise the predicate is malformed and the field stays visible. Parameters

Parameter	Type	Default	Description
`schema`	`JsonSchema`	—	—
`values`	`Record<string, unknown>`	—	—

Related: JsonSchema

resolveRef

function resolveRef(schema: JsonSchema, root: JsonSchema): JsonSchema

Resolve an internal $ref against the document root, following chained refs (a $ref whose target is itself a $ref). Only same-document pointers are supported (#/$defs/Name, #/definitions/Name, #); an external or unresolvable ref throws LOUDLY rather than yielding a silent empty schema. A schema with no $ref is returned unchanged. A pointer cycle throws. Parameters

Parameter	Type	Default	Description
`schema`	`JsonSchema`	—	—
`root`	`JsonSchema`	—	—

Related: JsonSchema

validateAgainstSchema

function validateAgainstSchema(
  schema: JsonSchema,
  value: unknown,
  options?: ValidateOptions,
): SchemaFormErrors

Validate value against schema, returning a per-path error bag (empty = valid). The caller runs this before submit and feeds the result back to SchemaForm for display. options.maxUploadBytes mirrors the renderer’s maxUploadBytes prop so a media field’s byte cap is enforced identically here; options.fieldWording puts a field’s own invalid sentence in place of the SDK’s word for any shape error on that field, and its own required sentence in place of the SDK’s message for a missing required value at or inside that field. Parameters

Parameter	Type	Default	Description
`schema`	`JsonSchema`	—	—
`value`	`unknown`	—	—
`options` (optional)	`ValidateOptions`	—	—

Related: JsonSchema, SchemaFormErrors

HTTP API

CLI

Settings

Capability map

Conversation bridge

Python SDK

Studio SDK

Schema forms

CompletionProvider

DateRangePair

Discriminator

ExpressionFieldComponent

ExpressionFieldContext

ExpressionFieldProps

ExpressionInputKey

ExpressionInputShape

FieldWords

FormControl

FormInputMode

JsonSchema

JsonSchemaType

NoFiniteValueError

RecordEntryContext

RecordEntryRenderer

RecordEntryRendererContext

SchemaForm

SchemaFormErrors

SchemaFormProps

SecretRef

SecretRefField

SecretRefFieldProps

TemplatedTextCatalogContext

UseTemplatedTextCatalog

dateRangePairs

defaultValueForSchema

fieldDrawingOrder

isFieldVisible

resolveRef

validateAgainstSchema

​CompletionProvider

​DateRangePair

​Discriminator

​ExpressionFieldComponent

​ExpressionFieldContext

​ExpressionFieldProps

​ExpressionInputKey

​ExpressionInputShape

​FieldWords

​FormControl

​FormInputMode

​JsonSchema

​JsonSchemaType

​NoFiniteValueError

​RecordEntryContext

​RecordEntryRenderer

​RecordEntryRendererContext

​SchemaForm

​SchemaFormErrors

​SchemaFormProps

​SecretRef

​SecretRefField

​SecretRefFieldProps

​TemplatedTextCatalogContext

​UseTemplatedTextCatalog

​dateRangePairs

​defaultValueForSchema

​fieldDrawingOrder

​isFieldVisible

​resolveRef

​validateAgainstSchema

CompletionProvider

DateRangePair

Discriminator

ExpressionFieldComponent

ExpressionFieldContext

ExpressionFieldProps

ExpressionInputKey

ExpressionInputShape

FieldWords

FormControl

FormInputMode

JsonSchema

JsonSchemaType

NoFiniteValueError

RecordEntryContext

RecordEntryRenderer

RecordEntryRendererContext

SchemaForm

SchemaFormErrors

SchemaFormProps

SecretRef

SecretRefField

SecretRefFieldProps

TemplatedTextCatalogContext

UseTemplatedTextCatalog

dateRangePairs

defaultValueForSchema

fieldDrawingOrder

isFieldVisible

resolveRef

validateAgainstSchema