[Request] Include file Hierarchy in api

[Kha-kis]

Hello UNIT3D Community Edition Team,

I hope this message finds you in good spirits. Following the successful inclusion of the file_name in the JSON response of the /api/torrents/filter endpoint, for which I'm immensely grateful, I've identified another potential enhancement that could significantly improve the usability and functionality of the UNIT3D API. This feature would complement the previously added feature by providing even more context about the files.

Feature Request
Summary: Include the hierarchy of .torrent files in the JSON response of the /api/torrents/filter endpoint to allow identification of the parent folder name when it exists.

Detail: The inclusion of the torrent file hierarchy in the API responses would be a substantial improvement. It would enable users and developers to understand the structure of the torrents, including the parent folder name, which is often crucial for organizing and displaying torrent content effectively. This feature would be especially beneficial in scenarios where torrents contain multiple files organized in folders, making it easier to present and navigate through these files in applications.

Use Case
In my application, displaying the full hierarchy of torrent contents, including parent folders, is essential for users who rely on this structure to make informed decisions about which torrents to download. The current lack of this information in the endpoint's response necessitates cumbersome workarounds, such as making additional calls to fetch the torrent's metadata or relying on external sources to piece together this structure.

Proposed Solution
The ideal implementation would include a detailed representation of the torrent's file structure in the endpoint's response. This could be a nested JSON object that lists all files and folders, including the parent folder name when applicable, thus providing a comprehensive view of the torrent's contents directly through the API.

Additional Context
The absence of this feature limits the API's ability to fully support applications that require detailed insights into the structure of torrent files. By including the file hierarchy in the API responses, UNIT3D would significantly enhance its capabilities, making it a more versatile tool for developers and users alike.

Thank you for considering this enhancement. I am convinced that it would be a valuable addition to the UNIT3D API, further enriching its utility and effectiveness. I am eager to hear your thoughts and am ready to provide further clarification or assistance as needed.

Best regards,

Khakis

Upvote & Fund

• We're using Polar.sh so you can upvote and help fund this issue.
• We receive the funding once the issue is completed & confirmed by you.
• Thank you in advance for helping prioritize & fund our backlog.