Let us define a condition for Text In-line Filters.
With the previous code snippet, we have changed the default condition to be Ends With for Text In-line Filters.
If you add more than one condition to the custom instance, the DikeGrid will take only the first one.
Customization at the grid level
When you provide an Injection Token, you are changing conditions for all DikeGrid instances that live under the place you give the Injection Token.
Sometimes, you want to be specific for a particular DikeGrid instance. Then, to change conditions at the grid scope, you must provide the corresponding custom instance through an input property named gridCustomFilterConditions.
The gridCustomFilterConditions property is of type DikeGridCustomFilterConditions. You can not change this property at runtime.
Let us provide custom conditions for Date and Numeric types.
We have changed the Date condition to be Greater Than and the Numeric condition to be grid-customRowNumericMultipleOf.
For Date types, we took an existing condition, and for Numeric types, we defined a new custom condition.
Summary
In-line Filters are the quickest and easiest way to enable filtering. Every filter type has a default condition attached, but you can change it by providing a custom condition definition.