github/qBittorrent
1
0
Fork 0
mirror of https://github.com/qbittorrent/qBittorrent synced 2025-07-30 19:40:18 -07:00
Code Issues Projects Releases Packages Wiki Activity Actions 3
qBittorrent/WebAPI_Changelog.md
Thomas Piccirello 2ebe8595c9
Some checks failed
CI - File health / Check (push) Has been cancelled
Details
CI - macOS / Build (push) Has been cancelled
Details
CI - Python / Check (push) Has been cancelled
Details
CI - Ubuntu / Build (push) Has been cancelled
Details
CI - WebUI / Check (push) Has been cancelled
Details
CI - Windows / Build (push) Has been cancelled
Details
Modify CategoryOptions serialization to JSON 
When a category's download path option is set to "Default", its `downloadPath` is serialized into JSON as `undefined`. This results in the `downloadPath` field being omitted from `torrents/categories` and `torrents/maindata` payloads (as is expected with an `undefined` value).

The use of `undefined` here causes an issue in the WebUI. Specifically, when the category previously contained a value for this field (i.e. download path option set to either "Yes" or "No"), the `processMap` logic in `SyncController` does not detect the removal this field. This results in the category's new `downloadPath` not being properly sent to the client. By switching from `undefined` to `null`, we ensure that the `downloadPath` value is always included in the category's payload. This allows `processMap` to properly detect whenever the value changes.

This change is backwards compatible with existing categories.json files. Older qBittorrent versions should also be able to parse new categories.json files containing `null`.

More context: https://github.com/qbittorrent/qBittorrent/pull/22938/commits/cd3fbfbf9b63a42f1d4d9d48d0c2d20a5c1a4b28#r2173148696

PR #22958.
2025-07-07 00:17:57 +08:00

2.6 KiB
Raw Blame History

WebAPI Changelog

2.11.10

  • #22932
    • torrents/categories and sync/maindata now serialize categories' downloadPath to null, rather than undefined

2.11.9

  • #21015
    • Add torrents/fetchMetadata endpoint for retrieving torrent metadata associated with a URL
    • Add torrents/parseMetadata endpoint for retrieving torrent metadata associated with a .torrent file
    • Add torrents/saveMetadata endpoint for saving retrieved torrent metadata to a .torrent file
    • torrents/add allows adding a torrent with metadata previously retrieved via torrents/fetchMetadata or torrents/parseMetadata
    • torrents/add allows specifying a torrent's file priorities
  • #22698
    • torrents/addTrackers and torrents/removeTrackers now accept hash=all and adds/removes the tracker to/from all torrents
      • For compatibility, torrents/removeTrackers still accepts hash=* internally we transform it into all
    • Allow passing a pipe (|) separated list of hashes in hash for torrents/addTrackers and torrents/removeTrackers

2.11.8

  • #21349
    • Handle sending 204 No Content status code when response contains no data
      • Some endpoints still return 200 OK to ensure smooth transition
  • #22750
    • torrents/info allows an optional parameter includeFiles that defaults to false
      • Each torrent will contain a new key files which will list all files similar to the torrents/files endpoint
  • #22813
    • app/getDirectoryContent allows an optional parameter withMetadata to send file metadata
      • Fields are name, type, size, creation_date, last_access_date, last_modification_date
      • See PR for TypeScript types

2.11.7

  • #22166
    • sync/maindata returns 3 new torrent fields: has_tracker_warning, has_tracker_error, has_other_announce_error

2.11.6

  • #22460
    • app/setPreferences allows only one of max_ratio_enabled, max_ratio to be present
    • app/setPreferences allows only one of max_seeding_time_enabled, max_seeding_time to be present
    • app/setPreferences allows only one of max_inactive_seeding_time_enabled, max_inactive_seeding_time to be present