[Feature Request] more flexible command filtering for dynamic data

[HuakunShen]

Describe the feature in detail (code, mocks, or screenshots encouraged)

Currently the command component https://next.bits-ui.com/docs/components/command#custom-filter
has a shouldFilter prop to control filtering.

Can the prop be applied to Command.Group?

Here is a sample scenario:

1. I have multiple groups, 2 of them have fixed number of commands, ~10-20 each
2. Another command group contains hundreds of commands
   I can't provide all these commands, otherwise it will be too slow to render and filter. I have to set shouldFilter=false then do custom filter on it, but this also disabled default filtering for the other 2 small groups, and I lose the sorting by command score feature for all of them.

Proposed solution:

1. Make shouldFilter a prop for each group
2. Let each command group do their own custom filtering function

Moreover, it would be nice if the value field for command item can be js object rather than string.
Sometimes I have to JSON.stringify an object into value and JSON.parse in custom filtering function, this affects performance a lot.

What type of pull request would this be?

Enhancement

Provide relevant links or additional information.

No response

[huntabyte]

The value is what is used to search by, so that will remain a string. If you need to know when a user selects a certain value, creating a mapping of [key: value]: YourObject would be more performant than continuously stringifying/parsing the entire object.

At the moment, there isn't a plan to add granular group filtering, it's just custom filtering for all or default filtering for all. Perhaps it is something we can look into in the future should there be more demand.