WebAPI: Add "torrents/stats" endpoint to return per-state torrent counts #23535
+75
−0
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.
This PR adds a new WebAPI endpoint:
Purpose
For users with a large number of torrents,
/sync/maindatacan be expensive because it always returns full torrent metadata.This endpoint provides a lightweight alternative by returning only the counts of torrents per underlying
TorrentState, as requested in issue #23449.What it returns
A JSON object mapping each TorrentState to its torrent count.
Keys follow the existing WebAPI naming convention (snake_case), e.g.:
{
"downloading": 12,
"uploading": 4,
"queued_downloading": 5,
"stalled_downloading": 3,
"error": 2
// not putting all states here though
}
Implementation details
raw - minState) ensures O(n) performance with minimal overhead.Fixes
Fixes #23449