Clarify file order and indexes (#7120)

See the discussion in #5578. I don't think anyone would expect
otherwise, but it doesn't hurt to be explicit.
This commit is contained in:
Etienne Dechamps 2024-10-13 14:35:32 +01:00 committed by GitHub
parent f0af1fb0ab
commit 32cfd712d0
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 2 additions and 1 deletions

View File

@ -300,8 +300,9 @@ The 'source' column here corresponds to the data structure there.
| `beginPiece` | number | tr_file_view
| `endPiece` | number | tr_file_view
Files are returned in the order they are laid out in the torrent. References to "file indices" throughout this specification should be interpreted as the position of the file within this ordering, with the first file bearing index 0.
`fileStats`: a file's non-constant properties. An array of `tr_info.filecount` objects, each containing:
`fileStats`: a file's non-constant properties. An array of `tr_info.filecount` objects, in the same order as `files`, each containing:
| Key | Value Type | transmission.h source
|:--|:--|:--