Shadcn Filters Choice Controls

When to use

• Toolbars of removable filter chips over a table or list, one field, condition and value per chip
• Nested AND and OR condition builders, hung off a trigger over a report or laid out inline
• Attribute catalogs too large or deep to list at once, and option lists paged from a server

When not to use

• Option lists drawn by the built in menu with picks pinned on top: use the Filters Full Filter Bar example
• A finished record table with its chip bar, paging and row actions already built: use the Filtering blocks
• Storefront product facets with price sliders, color swatches and department pills: use the Filter Sidebar blocks
• One day or span of days picked on its own, with no attribute or condition: use the Date Selector component

Agent notes

• Each editor reads its rows from a constant such as CHANNELS or PERMISSIONS, not the field's options, so reusing it elsewhere shows the wrong rows
• Pass commit a second argument with close set to false to keep the panel open, as ChannelToggles and PermissionChecks do
• renderValue, icon and a component editor count toward the schema index by presence only, so swapping one alone keeps serving the old one
• A rule reaches onQueryChange unfinished: an empty operator, or a value still undefined or empty where its arity is not none; skip it when compiling
• Negate swaps to an operator's inverse where one exists and otherwise sets negated, as on starts_with, so a compiler must read negated