Primitive data types are the building blocks for component data. They represent simple values like text, numbers, and booleans.
The text data type accepts string values with optional validation constraints. These ensure data quality and guide users toward valid input.
Note: Specify these additional configurations under a text field in your data item.
Maximum number of characters allowed.
Minimum number of characters required.
Regular expression pattern the text must match.
Note: If you set a defaultValue, it populates the panel's text input when the component is first added. If a Wix user then deletes the text, the field remains empty, it doesn't revert to the default.
A text field with validation constraints:
In the manifest:
In the component:
The guid data type represents a globally unique identifier (GUID/UUID). No additional configuration is needed.
A GUID field for unique identification:
In the manifest:
In the component:
The number data type accepts numeric values with optional validation constraints. Useful for ensuring values stay within acceptable ranges.
Note: Specify these additional configurations under a number field in your data item.
Minimum allowed value.
Maximum allowed value.
Multiplier applied to the value.
All 3 fields are optional, and all 3 take strings rather than numbers. Set them when the value has a meaningful range, so the editor can render a bounded control instead of an open number input.
Note: These constraints and the item's defaultValue configure the editor panel. They don't reach your component. Give every numeric prop a default in your component code, so it has a value to render before a Wix user sets one. For more information, see Default values and runtime fallbacks.
A rating field with min and max constraints:
In the manifest:
In the component:
The booleanValue data type represents true or false values.
A feature toggle field:
In the manifest:
In the component:
Last updated: 2 November 2026