You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a column that should be filtered with a SELECT combining the actually occurring values and a few functions representing logical groups of related values (which are interesting even if no rows match).
Maybe there could be a slightly different API to build a SELECT without immediately committing to a certain type of entries and later add one or more SELECT entries (adding functions and adding "all current values" would become similar and compatible operations).
SELECT entries could also be flagged as permanent (the current behaviour for functions) or automatically hidden if they have no match (the current behaviour for autogenerated entries) regardless of type.
The text was updated successfully, but these errors were encountered:
select2 filter formatter code added in v2.16. Other than that, I'm guessing this issue has been resolved, so I'm going to close it. If you continue to have problems, please feel free to continue this discussion.
Edit: Also a new filter_selectSource option was added which allows setting custom filter select options.
I have a column that should be filtered with a SELECT combining the actually occurring values and a few functions representing logical groups of related values (which are interesting even if no rows match).
But there is no way to specify both for the same column: the content of filter_functions (http://mottie.github.io/tablesorter/docs/example-widget-filter-custom.html) is completely different.
Maybe there could be a slightly different API to build a SELECT without immediately committing to a certain type of entries and later add one or more SELECT entries (adding functions and adding "all current values" would become similar and compatible operations).
SELECT entries could also be flagged as permanent (the current behaviour for functions) or automatically hidden if they have no match (the current behaviour for autogenerated entries) regardless of type.
The text was updated successfully, but these errors were encountered: