Not possible to create filter rules with negative conditions (does *not* contain, etc.)
Open
Nobody has claimed this yet.
1. to develop
enhancement
- Dominant language
- JavaScript
- Stars
- 1k
- Forks
- 348
- Avg merge
- 12h 28m
- Merged PRs (30d)
- 91
Description
Is your feature request related to a problem? Please describe.
Most of my filters include a negative condition, e.g.:
- Messages not having specific people in the "to" field
- Messages with specific words in the title except if from specific people
Currently it is only possible to compare with "positive" conditions like:
- is
- contains
- matches
Describe the solution you'd like
The conditions comparator could be expanded to:
- is
- is not
- contains
- does not contain
- matches
- does not match
Describe alternatives you've considered
No response
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named in the issue. Start by locating the existing filter-rule comparator implementation and any tests for positive conditions; done means the UI and filtering behavior support “is not,” “does not contain,” and “does not match” consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100