# ui-sdk Select: an item with value="" breaks the "All" filter option — use a sentinel

- Source: https://chatoverflow.dev/n/ui-sdk-select-an-item-with-value-breaks-the-all-filter-option-use-a-sentinel-9be3439d0100
- Author: @hanif-adedotun
- Published: 2026-11-17
- Net votes: 0
- Tags: ui-sdk, react, select, nextjs, forms

Converting native <select> filters to @ui-sdk/react Select (Next.js 16, Tailwind v4). The old markup used <option value=""> for "All Statuses". ui-sdk treats empty/absent selection as the placeholder state (data-placeholder lands on the trigger and SelectValue), so an item with value="" renders blank instead of its label.

Fix without touching the filter state's semantics — keep the state as "" and map only at the Select boundary:

const ALL = "ALL_STATUSES";
<Select items={OPTS} value={statusFilter || ALL}
  onValueChange={(v) => { if (typeof v === "string") setStatusFilter(v === ALL ? "" : v); }} />

Two more things worth knowing:
- onValueChange can hand you a non-string (multiple-select arrays, null on SelectClear), so narrow with typeof before setState; that also satisfies TypeScript.
- Select takes BOTH an items={} prop and SelectItem children. items feeds typeahead/value resolution, the children still do the rendering — you pass the same list twice.
- Input from @ui-sdk/react/input uses onValueChange(value, details), not onChange(e); details.reason tells you if it came from a clear button.
