-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add stalled filters to GUI and Web API/UI #11825
Add stalled filters to GUI and Web API/UI #11825
Conversation
Is it possible to use them in WebUI/GUI? |
Nope, it is not currently possible, and I did not touch the WebUI/GUI code. Should I include that in this PR, or is that content for a separate one? |
I think it should be included in this PR. The changes would not be very useful if it cannot be used. |
2b101ec
to
d9ba202
Compare
Well, the changes are usable via the WebAPI. Still, I agree that all interfaces should benefit from the change, so I now also implemented the filtering on the WebUI and GUI. Should I keep the WebAPI version bump commit? These changes could be part of the API version 2.4.0 just as well. |
I'm not really sure. I guess the version should bump only if it hasn't been done before. |
Let's also not forget ping @Piccirello to review the webUI/webAPI parts. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
The last release used 2.4.0 so we'll have to bump the version for these changes. It seems we use a modified semantic versioning: the minor version (x.Y.z) is bumped for breaking changes, and the patch version (x.y.Z) is bumped for new features and bug fixes. The last release probably should have used 2.3.1 instead of 2.4.0. Nevertheless, this will be 2.4.1. |
API versioning has compatibility related semantic: the patch version (x.y.Z) is bumped when we don't break current clients compatibility, and the minor version (x.Y.z) is bumped when we do it. I.e. clients that implement support of API x.y.z remain compatible with all the upcoming API x.y.*. |
df6d8d4
to
f0ce709
Compare
@FranciscoPombal |
`/api/v2/torrents/info` can now take the following new values for the`filter` parameter: `stalled`, `stalled_uploading` and `stalled_downloading`. Requires Web API version bump. Closes qbittorrent#11787
f0ce709
to
df2fbb1
Compare
@Chocobo1 done. |
Since entire app are affected you can (should) rename both PR/commit: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM (for code)
@sledgehammer999 |
Instead of saying "stalled", we could use something more descriptive like utorrent does. |
That sounds like a good idea, but it is a little out of scope for this PR and involves some more thorough changes. |
I'm not sure it correctly describes what is really happening... |
@FranciscoPombal |
Thanks. |
/api/v2/torrents/info
can now take the following new values for thefilter
parameter:stalled
,stalled_uploading
andstalled_downloading
.Requires Web API version bump.
Closes #11787
Screenshots:
GUI:

WebUI:
