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.
Reverts migration added in #14323 because it caused errors and I'm not sure that property is even done right.
Still making the caseSensitive optional since it's a false-default bool that can just as easily be omitted when typing other options, just for ease of configuration.
As for the filterable option - not really sure it's done right like that. For one, it's pretty odd to have to explicitly set true when you're already providing filtering options and it's more/less implied you want filtering. Also, pretty hard to find a use case for it in the spec. It's implemented separately at least as disableFiltering in WC, though that spec or the design handoff also don't discuss use cases for it.
At the very least - we should clear up that and also the options handling should probably merge setting w/ defaults, see WC implementation.
Additional information (check all that apply):
[ ] Bug fix
[ ] New functionality
[ ] Documentation
[ ] Demos
[ ] CI/CD
Checklist:
[ ] All relevant tags have been applied to this PR
[ ] This PR includes unit tests covering all the new code (test guidelines)
[ ] This PR includes API docs for newly added methods/properties (api docs guidelines)
[ ] This PR includes feature/README.MD updates for the feature docs
[ ] This PR includes general feature table updates in the root README.MD
[ ] This PR includes CHANGELOG.MD updates for newly added functionality
[ ] This PR contains breaking changes
[ ] This PR includes ng update migrations for the breaking changes (migrations guidelines)
[ ] This PR includes behavioral changes and the feature specification has been updated with them
Reverts migration added in #14323 because it caused errors and I'm not sure that property is even done right. Still making the
caseSensitiveoptional since it's a false-default bool that can just as easily be omitted when typing other options, just for ease of configuration.As for the
filterableoption - not really sure it's done right like that. For one, it's pretty odd to have to explicitly settruewhen you're already providing filtering options and it's more/less implied you want filtering. Also, pretty hard to find a use case for it in the spec. It's implemented separately at least asdisableFilteringin WC, though that spec or the design handoff also don't discuss use cases for it. At the very least - we should clear up that and also the options handling should probably merge setting w/ defaults, see WC implementation.Additional information (check all that apply):
Checklist:
feature/README.MDupdates for the feature docsREADME.MDCHANGELOG.MDupdates for newly added functionalityng updatemigrations for the breaking changes (migrations guidelines)