Select Component Lost Type Safety Since v1.0

[macmillen]

The Select component's type definitions appear to be missing or incomplete since version 1.0. This prevents its proper use with literal types, breaking type safety and requiring workarounds like type casting.

For example, the following code, which worked prior to v1.0, is now causing type errors:

const items: "mango" | "apple" | "kiwi" = ["mango", "apple", "kiwi"]

<Select.Root
  type="single"
  {items}
  onValueChange={(selected) => {
    // selected is now just a string
  }}
>

[huntabyte]

This was a decision made due to popular demand and a bunch of headaches people ran into for the more simple/common use cases for select components. It also enables us to provide form autofill, rendering a hidden select with values that can be submitted with forms, etc.

This keeps the primitive "primitive", and if you want to recreate the previous version you can easily do so by using a generic wrapper component that handles the types for you given a prop.