add support for not splitting "contains" value #6773
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've encountered situations where I wanted to filter out images with a blacklist of words in the filename (e.g. "low res", "lr", "preview", as well as their capitalized version) and the filter gets verbose really quickly. The "contains" function would be perfect to avoid this, but as of now you are forced to split the "values" parameter, which makes it unusable for filenames and such, and only useful for tags.
This could be a possible enhancement, where if the third parameter "separator" is set to "None" then the value won't get split, extending the function purposes.