Support more complex searches in filter by default #38
Labels
Milestone
Comments
TonyGermaneri
added a commit
that referenced
this issue
Sep 4, 2017
…e selectionMode = row. Added more complex search logic see issue #38. Renamed attribute childGridAttributes to cellGridAttributes deprecating childGridAttributes. Updated debug display to show more info horizontally. Fixed a bug in selection values when columns are hidden. Fixed a bug in copy where non-string values would crash the copy function. Updated touch default values to less sub-optimal values, still considered a wip. Truncating autocomplete items to maxAutoCompleteItems=200. Updated docs.
|
This feature is now implemented. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, it is not clear the filter is a regexp interface. This means laymen cannot search for strings that contain reserved characters (such as parentheses). Instead of just straight regexp interface, we should use a string pattern to switch regex on and off.
/<pat>/<flags>is the standard pattern. So any string matching this pattern will be considered regexp and parsed accordingly. Further, on error of regexpself.invalidFilterRegEx = e;should be set to the regexp error. If not using regex (pattern does not match/<pat>/<flags>) thenself.invalidFilterRegEx = false;should be set to booleanfalse. When using regex and no error has been detectedself.invalidFilterRegEx = true;should be set to boolean true to give a visual cue to the user that they are using regex and not just string matching.The text was updated successfully, but these errors were encountered: