Skip to content

feat: exclude subpaths in feeds - #1629

Open
SnoutFirst wants to merge 2 commits into
QuiteRSS:masterfrom
SnoutFirst:exclude-subpaths-feature
Open

feat: exclude subpaths in feeds#1629
SnoutFirst wants to merge 2 commits into
QuiteRSS:masterfrom
SnoutFirst:exclude-subpaths-feature

Conversation

@SnoutFirst

Copy link
Copy Markdown

Implements a feature to exclude specific subpaths from feeds.

@SnoutFirst

Copy link
Copy Markdown
Author

Replaced by #1630 to remove unrelated commits.

@SnoutFirst

Copy link
Copy Markdown
Author

Branch force-pushed to contain only the single relevant commit: Add excludeSubPaths feature to filter feed items by URL patterns.

@SnoutFirst

Copy link
Copy Markdown
Author

Temporarily closing to refresh branch state after force-push.

@SnoutFirst SnoutFirst closed this Jul 13, 2026
@SnoutFirst SnoutFirst reopened this Jul 13, 2026
- Add excludeSubPaths field to feed properties dialog
- Store exclusion patterns as comma-separated list in database (v18)
- Filter news items at parse time based on URL patterns
- Support case-insensitive partial URL matching
- Useful for blocking YouTube Shorts, Facebook Reels, etc.
@SnoutFirst
SnoutFirst force-pushed the exclude-subpaths-feature branch from 83f0942 to 08465be Compare July 13, 2026 22:47
Commit 6bd1ae5 (cleanup: remove remaining dead webkit/embedded browser
code) removed javaScriptEnable from the feed properties UPDATE query,
reducing the placeholder count from 15 to 14.

Commit 55ea278 (Add excludeSubPaths feature) added excludeSubPaths to
the query and its bind value on a separate branch, making it 16
placeholders and 16 bind values.

The merge at 402417c resolved the conflict incorrectly: it kept the
left side's query (without javaScriptEnable AND without excludeSubPaths
— 14 placeholders) but kept the right side's bind values (with
excludeSubPaths — 15 bind values). This caused the excludeSubPaths value
to be bound to the id position, and feedId to be silently ignored,
meaning the UPDATE targeted the wrong row (or no row at all).

The result: the disableUpdate checkbox (and any other field in the
UPDATE) appeared to save but was actually updating a non-existent or
wrong row, so the change was lost on next app launch.

Fix: add excludeSubPaths = ? back to the UPDATE query so placeholders
and bind values match. Also add the missing model update (setData) for
excludeSubPaths so the in-memory model stays in sync.
@SnoutFirst

Copy link
Copy Markdown
Author

Pushed an additional fix commit (ed4f44f) that fixes a regression introduced by the merge of this branch: the disableUpdate checkbox in feed Properties was not being persisted because the model update (setData) for excludeSubPaths was missing. The database UPDATE query already had the correct bind values, but the in-memory model wasn't being updated, so the change was lost on next app launch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant