-
-
Notifications
You must be signed in to change notification settings - Fork 12
Compound Filters
- Available Types
- SASS Styling
- Compound Input Filter
- Compound Date Filter
- Compound Operator List (custom list)
- Compound Operator Alternate Texts
- Filter Complex Object
- Update Filters Dynamically
- How to avoid filtering when only Operator dropdown is changed?
Compound filters are a combination of 2 elements (Operator Select + Input Filter) used as a filter on a column. This is very useful to make it obvious to the user that there are Operator available and even more useful with a date picker (Flatpickr
).
There are multiple types of compound filters available
-
Filters.compoundInputText
adds an Operator combine to an Input of typetext
(alias toFilters.compoundInput
). -
Filters.compoundInputNumber
adds an Operator combine to an Input of typenumber
. -
Filters.compoundInputPassword
adds an Operator combine to an Input of type `password. -
Filters.compoundDate
adds an Operator combine to a Date Picker (flatpickr). -
Filters.compoundSlider
adds an Operator combine to a Slider Filter.
You can change the $flatpickr-bgcolor
and any of the $compound-filter-X
SASS variables for styling. For more info on how to use SASS in your project, read the Wiki - Styling
Simply set the flag filterable
to True and use the filter type Filters.compoundInput
. Here is an example with a full column definition:
// define you columns, in this demo Effort Driven will use a Select Filter
const columnDefinitions = [
{ id: 'title', name: 'Title', field: 'title' },
{ id: 'description', name: 'Description', field: 'description', filterable: true },
{ id: 'complete', name: '% Complete', field: 'percentComplete',
formatter: Formatters.percentCompleteBar,
type: FieldType.number,
filterable: true,
filter: { model: Filters.compoundInput }
}
];
// you also need to enable the filters in the Grid Options
const gridOptions = {
enableFiltering: true
};
The column definition type
will affect the list of Operators shown, for example if you have type: FieldType.string
, it will display the operators (=
, a*
, *z
) where a*
means StartsWith and *z
means EndsWith. The current logic implemented is that any types that are not String, will display the list of Operators (
, =
, <
, <=
, >
, >=
, <>
)
Again set the column definition flag filterable: true
and use the filter type Filters.compoundDate
. Here is an example with a full column definition:
// define you columns, in this demo Effort Driven will use a Select Filter
const columnDefinitions = [
{ id: 'title', name: 'Title', field: 'title' },
{ id: 'description', name: 'Description', field: 'description', filterable: true },
{ id: 'usDateShort', name: 'US Date Short', field: 'usDateShort',
type: FieldType.dateUsShort,
filterable: true,
filter: {
model: Filters.compoundDate,
// you can also add an optional placeholder
placeholder: 'filter by date'
}
}
];
// you also need to enable the filters in the Grid Options
const gridOptions = {
enableFiltering: true
};
this.setState((state: State) => ({
...state,
gridOptions,
columnDefinitions,
dataset: this.getData(),
}));
What if your date input (from your dataset) has a different output on the screen (UI)?
In that case, you will most probably have a Formatter and type representing the input type, we also provided an outputType
that can be used to deal with that case.
For example, if we have an input date in UTC format and we want to display a Date ISO format to the screen (UI) in the date picker.
// define you columns, in this demo Effort Driven will use a Select Filter
const columnDefinitions = [
{ id: 'title', name: 'Title', field: 'title' },
{ id: 'description', name: 'Description', field: 'description', filterable: true },
{ id: 'utcDate', name: 'UTC Date', field: 'utcDate',
type: FieldType.dateUtc, // format used in the dataset (input)
formatter: Formatters.dateTimeIso, // format to show in the cell on each row (formatter)
outputType: FieldType.dateTimeIso, // format to show in the date picker
filterable: true, filter: { model: Filters.compoundDate }
}
];
// you also need to enable the filters in the Grid Options
const gridOptions = {
enableFiltering: true
};
The date picker will automatically detect if the type
or outputType
has time inside, if it does then it will add a time picker at the bottom of the date picker.
For example, if we have an input date in UTC format and we want to display a Date ISO format with time to the screen (UI) and the date picker.
// define you columns, in this demo Effort Driven will use a Select Filter
const columnDefinitions = [
{ id: 'title', name: 'Title', field: 'title' },
{ id: 'description', name: 'Description', field: 'description', filterable: true },
{ id: 'utcDate', name: 'UTC Date', field: 'utcDate',
type: FieldType.dateUtc,
formatter: Formatters.dateTimeIsoAmPm,
outputType: FieldType.dateTimeIsoAmPm,
filterable: true, filter: { model: Filters.compoundDate }
}
];
// you also need to enable the filters in the Grid Options
const gridOptions = {
enableFiltering: true
};
All the available options that can be provided as filterOptions
to your column definitions can be found under this FlatpickrOption interface and you should cast your filterOptions
to that interface to make sure that you use only valid options of the Flatpickr library.
filter: {
model: Filters.compoundDate,
filterOptions: {
minDate: 'today'
} as FlatpickrOption
}
In order to use different locale, you will have to import whichever Flatpickr locale you need. The best place to do these imports is in your App Module so it's global and you do it only once.
// load necessary Flatpickr Locale(s), but make sure it's imported AFTER loading Slickgrid-React plugin
// delaying the import will work for our use case
setTimeout(() => import('flatpickr/dist/l10n/fr'));
Each Compound Filter will try to define the best possible Operator List depending on what Field Type you may have (for example we can have StartsWith Operator on a string but not on a number). If you want to provide your own custom Operator List to a Compound Filter, you can do that via the compoundOperatorList
property (also note that your Operator must be a valid OperatorType/OperatorString).
const columnDefinitions = [
{ id: 'title', name: 'Title', field: 'title' },
{ id: 'description', name: 'Description', field: 'description', filterable: true },
{ id: 'utcDate', name: 'UTC Date', field: 'utcDate',
type: 'dateUtc',
formatter: Formatters.dateTimeIsoAmPm,
outputType: 'dateTimeIsoAmPm',
filterable: true, filter: {
model: Filters.compoundSlider,
// here is our custom list that will override default list
compoundOperatorList: [
{ operator: '', desc: '' },
{ operator: '=', desc: 'Equal to' },
{ operator: '<', desc: 'Less than' },
{ operator: '>', desc: 'Greater than' },
]
}
}
];
You can change any of the compound operator text or description shown in the select dropdown list by using compoundOperatorAltTexts
to provide alternate texts.
Note make sure to not use more than 2 or 3 characters for the operator text, exceeding that will require CSS style changes.
this.gridOptions = {
compoundOperatorAltTexts: {
// where '=' is any of the `OperatorString` type shown above
numeric: { '=': { operatorAlt: 'eq', descAlt: 'alternate numeric equal description' } },
text: { '=': { operatorAlt: 'eq', descAlt: 'alternate text equal description' } }
},
}
Starting with version >=5.1.x
, you can now enable skipCompoundOperatorFilterWithNullInput
that can be provided to your Grid Options (or via global grid options) and/or your Column Definition.
What will this option do really?
- skip filtering (in other words do nothing) will occur when:
- Operator select dropdown (left side) is changed without any value provided in the filter input (right).
- start filtering when:
- Operator select dropdown is changed and we have a value provided in the filter input, it will start filtering
- Operator select dropdown is empty but we have a value provided in the filter input, it will start filtering
Note the Compound Date Filter is the only filter that has this option enabled by default.
const columnDefinitions = [{
id: 'name', field: 'name',
filter: {
model: Filters.compoundInput,
skipCompoundOperatorFilterWithNullInput: true // change via column def, always has higher specificity over grid options
}
}];
// or change for all compound filters of the same grid
const gridOptions = {
skipCompoundOperatorFilterWithNullInput: true,
};
Contents
- Slickgrid-React Wiki
- Installation
- Styling
- Interfaces/Models
- Column Functionalities
- Global Grid Options
- Localization
- Events
- Grid Functionalities
- Auto-Resize / Resizer Service
- Resize by Cell Content
- Add/Delete/Update or Highlight item
- Dynamically Change Row CSS Classes
- Column Picker
- Composite Editor Modal
- Context Menu
- Custom Tooltip
- Excel Copy Buffer
- Export to Excel
- Export to File (CSV/Txt)
- Grid Menu
- Grid State & Presets
- Grouping & Aggregators
- Header Menu & Header Buttons
- Header Title Grouping
- Pinning (frozen) of Columns/Rows
- Row Colspan
- Row Detail
- Row Selection
- Tree Data Grid
- SlickGrid & DataView objects
- Addons (controls/plugins)
- Backend Services