Choose proper combo filtering options

IgniteUI / igniteui-angular

Ignite UI for Angular is a complete library of Angular-native, Material-based Angular UI components with the fastest grids and charts, Pivot Grid, Dock Manager, Hierarchical Grid, and more.

https://www.infragistics.com/products/ignite-ui-angular

Other

568 stars 159 forks source link

Choose proper combo filtering options #14340

Open Lipata opened 3 weeks ago

Lipata commented 3 weeks ago

Description

The removal of filterable property and integration inside the filteringOptions needs to be reconsidered. The main reason is that in igniteui-webcomponents combo they are separated. If this is a better approach, we should apply it back in the igniteui-angular combo, accompanied by the proper migration. We should consider if we need the boolean filterable property at all.

More info: https://github.com/IgniteUI/igniteui-angular/pull/14339#issue-2338455618

Lipata commented 3 weeks ago

@sdimchevski we will need your input on that matter:

do we need to have a filtereable boolean option at all? Filtering is something you always expect to work and should always be enabled.
if we need such an option, should it be a separate property, like it is in web components, or should it be part of the filtering options object, like it is in angular?

ChronosSF commented 3 weeks ago

@kacheshmarova , on the meeting today we decided to remove the filterable property from the filtering options entirely.