feat: select field filter options

[jacobsfletch]

It is a common pattern to dynamically show and validate a select field's options based on various criteria such as the current user or underlying document.

Some examples of this might include:

• Restricting options based on a user's role, e.g. admin-only options
• Displaying different options based on the value of another field, e.g. a city/state selector

While this is already possible to do with a custom validate function, the user can still view and select the forbidden option...unless you also wired up a custom component.

Now, you can define filterOptions on select fields.

This behaves similarly to the existing filterOptions property on relationship and upload fields, except the return value of this function is simply an array of options, not a query constraint. The result of this function will determine what is shown to the user and what is validated on the server.

Here's an example:

{
  name: 'select',
  type: 'select',
  options: [
    {
      label: 'One',
      value: 'one',
    },
    {
      label: 'Two',
      value: 'two',
    },
    {
      label: 'Three',
      value: 'three',
    },
  ],
  filterOptions: ({ options, data }) =>
    data.disallowOption1
      ? options.filter(
          (option) => (typeof option === 'string' ? options : option.value) !== 'one',
        )
      : options,
}

---

• To see the specific tasks where the Asana app for GitHub is being used, see below:
  • https://app.asana.com/0/0/1210524295135089

[DanRibbens]

Are we married to reduceOptions, I would prefer to just call it filterOptions?

[github-actions]

🚀 This is included in version v3.40.0