OptionalclearClear the value (remove the key from the submission data) when the field is hidden. This is applied if the component itself or any parent is hidden, irrespective the mechanism that made it hidden.
Related: hidden, conditional.
OptionalconditionalOptionaleq?: string | number | booleanThe value that should be checked against the reference component value.
For array values (of the reference component), the array is checked if it contains the specified value.
Optionalshow?: booleanWhether the field should be shown (true) or hidden (false) when the condition
is met.
Optionalwhen?: stringThe reference component key. Its value will be retrieved and tested against eq.
OptionaldescriptionAdditional information for the form field, displayed unconditionally.
OptionalhiddenHide or show the form field. This only controls the visibility - whether
submission data is retained or not is controlled through clearOnHide.
Unique ID for a component in a form definition. Used to render HTML IDs.
OptionalisMarker for a form field that requests potentially (privacy) sensitive information.
Pruning of submission data will clear the data of components marked as sensitive data.
This is specific to Open Forms.
Unique key for the component in a larger form definition.
The value must comply with the (\w|\w[\w.\-]*\w) regex, meaning that periods/dots
are allowed unless they're start or end. The period character creates a nesting
level in the submission data.
The form field label text.
OptionalopenOptionalregistrationConfiguration on how to process the value of the component in the registration plugin(s).
OptionaltooltipExtra information or background for the form field. Displayed after interacting with the tooltip icon/control near the label.
Discriminator to determine the component type. Uniquely determines the shape of the component configuration options.
Component shape/options for the partners (family members) component.
The submission data type is always an array of
PartnerDetails, even if at most one partner is expected.Remarks
The generated documentation might be slightly off due to rendering the type alias as an interface. Double check with the actual TS types!