hydrusnetwork / hydrusnetwork/hydrus
RfE: a "reverse" string match feature for content parser results
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.2k
- Forks
- 207
- PR merge metrics
- No merged PRs in 30d
Description
would it be able to implement a string match feature that does the exact opposite of what string match currently does?
instead of returning the results that it matches with, simply dont return any results that the string matches with. sort of like a wildcard blacklist inside the content parser, if you will
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
Start by locating the existing string-match behavior in the content parser and tracing how matched results are returned. Define the inverse behavior so matching results are excluded, then add coverage showing that both matching and non-matching results are handled correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100