Case sensitivity of filter operators #2062
geneticdrift
started this conversation in
Ideas
Replies: 1 comment
-
Added PR #2064 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Currently the case sensitivity of filter operators is determined by the command.
For example the
contains
operator is case sensitive inlist
command and case-insensitive insearch
.It means that for a case-insensitive
list
command a new command needs to be added, likesearchcount
was added for case-insensitive version ofcount
.It also means that it's impossible to have case-sensitive and case-insensitive operators mixed in the same filter.
Would it make sense to add operators that are explicitly case-sensitive or not that can be used with any command which will override the default case-sensitivity of the command?
Proposed new operators:
unchanged:
depends on command
case-sensitive
case-insensitive
Beta Was this translation helpful? Give feedback.
All reactions