To use date filtering it is necessary to specify the new 'type' attribute to the column component and set it to 'date'. It's wasn't possible to determine the type of the column just based on the filterBy property. An initial attempt was made to deduce the type based on the first row, but when there are no rows or if the column value of the first row was null, there was no way to determine the type. For example, when trying to filter a date for which there are no matches. After that, the table component didn't render the calendar for the filter field of the date column. So, with this new attribute, we're starting to make ace:dataTable more aware of the value types it contains, as mobi:dataView does. Up to now, all filtering had been treated as a string.

The commit above adds the ability to filter rows based on a single date. Adding ranges in general, whether they are date ranges or numeric ranges, would require major changes in our code. The main reasons are that the filterValue property of columns is of type String and can only hold one value. An idea is to add another attribute to the Column component called filterRange, which is associated to a special object containing two data values. Also, the Predicates would need to be modified to use two values or a new Predicate would need to be used. However, it's still not clear how things would work when using a global filter.

New JIRA for general range filtering support makes sense, and this one can depend on the new one.

The range filtering capability was committed under ICE-10811.