Expand extraction rules to deny content based on selectors
Open
complexity:high
enhancement
priority:medium
- Dominant language
- Ruby
- Stars
- 224
- Forks
- 48
- Avg merge
- 23h 16m
- Merged PRs (30d)
- 18
Description
### Problem Description
Currently it's only possible to restrict content ingested within a page using data extraction attributes, which requires control over the website source code.
It should be easy to add an extraction rule that denies content that follows a specified CSS or XPath selector (basically the opposite of what extraction rules do now).
### Proposed Solution
Expand extraction rules to support denying content.
Contributor guide
Assessment
This issue has not been assessed yet.