Interface

FieldBoundAddonActionContext

@ng-forge/dynamic-forms

Field-bound variant — the addon is attached to a real field and has a working value-writer. The common case for pi-button / mat-button / bs-button / ion-button inside an adapter input field.

setValue is non-optional here; the optional chain (ctx.setValue?.()) is unnecessary noise once you've narrowed via {@link isFieldBoundContext}.

Signature

interface FieldBoundAddonActionContext<
  TValue = unknown
>
  extends AddonActionContextBase<TValue>

Type Parameters

Name	Constraint	Default	Description
`TValue`	`-`	`unknown`	-

Properties

Name	Type	Description
`form`	`ReadonlyFieldTree<TValue>`	Read-only view of the host field's tree — same view wrappers receive.
`setValue`	`(next: TValue) => void`	Push a new value into the host field.

packages/dynamic-forms/src/lib/models/addon/addon-action.ts:31