Parent issue: #275
The torrent details endpoint response GET /v1/torrent/INFO_HASH does not include the info for the canonical infohash group. It was a new concept introduced here.
This is the current response:
{
"data": {
"torrent_id": 2646,
"uploader": "username_600743",
"info_hash": "34b90c8b78e018d10c6c777d0e99d48fbf3cf5bf",
"title": "title-6a6b0929-8a53-4066-bd58-a160f7c36590",
"description": "description-6a6b0929-8a53-4066-bd58-a160f7c36590",
"category": {
"category_id": 5,
"name": "software",
"num_torrents": 148
},
"upload_date": "2023-09-14 15:52:55",
"file_size": 16,
"seeders": 0,
"leechers": 0,
"files": [
{
"path": [
"file-6a6b0929-8a53-4066-bd58-a160f7c36590.txt"
],
"length": 16,
"md5sum": null
}
],
"trackers": [
"udp://localhost:6969",
"udp://localhost:6969"
],
"magnet_link": "magnet:?xt=urn:btih:34b90c8b78e018d10c6c777d0e99d48fbf3cf5bf&dn=title-6a6b0929-8a53-4066-bd58-a160f7c36590&tr=udp%3A%2F%2Flocalhost%3A6969&tr=udp%3A%2F%2Flocalhost%3A6969",
"tags": [],
"name": "file-6a6b0929-8a53-4066-bd58-a160f7c36590.txt"
}
}It would be nice to include that information in the frontend.
And maybe we should rename the field info_hash to canonical_info_hash in the database and endpoint responses. See #283
Parent issue: #275
The torrent details endpoint response
GET /v1/torrent/INFO_HASHdoes not include the info for the canonical infohash group. It was a new concept introduced here.This is the current response:
{ "data": { "torrent_id": 2646, "uploader": "username_600743", "info_hash": "34b90c8b78e018d10c6c777d0e99d48fbf3cf5bf", "title": "title-6a6b0929-8a53-4066-bd58-a160f7c36590", "description": "description-6a6b0929-8a53-4066-bd58-a160f7c36590", "category": { "category_id": 5, "name": "software", "num_torrents": 148 }, "upload_date": "2023-09-14 15:52:55", "file_size": 16, "seeders": 0, "leechers": 0, "files": [ { "path": [ "file-6a6b0929-8a53-4066-bd58-a160f7c36590.txt" ], "length": 16, "md5sum": null } ], "trackers": [ "udp://localhost:6969", "udp://localhost:6969" ], "magnet_link": "magnet:?xt=urn:btih:34b90c8b78e018d10c6c777d0e99d48fbf3cf5bf&dn=title-6a6b0929-8a53-4066-bd58-a160f7c36590&tr=udp%3A%2F%2Flocalhost%3A6969&tr=udp%3A%2F%2Flocalhost%3A6969", "tags": [], "name": "file-6a6b0929-8a53-4066-bd58-a160f7c36590.txt" } }It would be nice to include that information in the frontend.
And maybe we should rename the field
info_hashtocanonical_info_hashin the database and endpoint responses. See #283