Add the possibility to define own filter rules

[gityhuber]

At the moment it is only possible to use the build in filter criteria. The used internal regex works as a 'contains' filter. But there can be usecases where a 'beginsWith' filter or other criterias are useful. Because of that there should be the possibility to define own filter rules.

[SteveTheTechie]

@mlh758 This sounds like a great idea. However, there is a question about how this would actually be implemented in the UI. If you have a regular select drop-down in the heading to pick a pre-defined filter rule (e.g. "Begins with:", "Contains number", etc.), wouldn't that seem a bit strange? (a normal select in the heading of an enhanced multi-select widget) Essentially, the problem becomes how to allow end users to "pick something" in the header of a widget that is essentially an "enhanced picker".

If you put a simple checkbox labeled "Pattern" to the right of the filter box, that could work, but then you have to consider what would types of simple "patterns" would be understandable and usable by end users... probably not regular expressions. Also, how would you communicate what a valid pattern is to those same end users.

I would suggest leaving this issue open until someone can suggest a creative UI approach for implementing this. (I don't have an approach for this so I am ignoring it.)

[mlh758]

I don't think they meant in the UI. They probably meant as an option to the filter plugin.