Skip to main content
The Select field stores one predefined option, or an ordered array of options when hasMany is enabled.
Options may be strings or { label, value } objects, and objects may add a color.

Config options

Filter options

filterOptions controls both which options appear in the admin panel and which values can be saved. It receives data, options, siblingData, and req, the current FrogBotRequest with req.frogbot, and must return the options synchronously. Common uses include restricting options by user role and changing available options based on another field.

Option colors

Give an option a color to show its value as a coloured pill in the admin panel.
color is one of seven names, the hues of the admin panel’s colour system: gray, blue, green, yellow, red, pink and purple. Each one follows the admin’s light or dark theme. The OptionColor type holds the same names:
Once any option has a colour, every value of the field shows as a pill. An option without a colour, and a stored value that matches no option, show as gray. A hasMany field shows one pill per value, in stored order. A field where no option has a colour looks the same as before. Pills appear in: The edit form and the List filters keep their usual controls. Colours are for display only. They don’t change stored values, validation, API responses or generated types. A custom admin.components.Cell replaces the pills in the List; Board and Calendar cards still show them. A name outside the list fails the type check, and FrogBot stops at startup with an error that names the field, the option and the allowed colours. cyan, teal and orange are no longer accepted; use blue, green or yellow.

Admin options

Select fields support the standard field admin options, plus these options:

Example

Custom components

Field

Server component

Client component

Label

Server component

Client component