Skip to content
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

[FR] Automatic Category Assignment #50

Closed
berot3 opened this issue Dec 14, 2021 · 2 comments
Closed

[FR] Automatic Category Assignment #50

berot3 opened this issue Dec 14, 2021 · 2 comments
Labels
feature request New feature or request status:more-info-needed More information is needed status:unlikely FR that are not out of scope for qbm

Comments

@berot3
Copy link

berot3 commented Dec 14, 2021

Basically this: qbittorrent/qBittorrent#5779 (open)

I guess qbit will never have this build in.

When is this useful: for ex. when adding a torrent manually and not category was giving. Instead of manually selecting a category this could be done by simple rules. See issue from above for more.

@bobokun bobokun added the feature request New feature or request label Dec 14, 2021
@bobokun
Copy link
Collaborator

bobokun commented Dec 14, 2021

In the newest develop branch I have it set the default category based on the last directory in it's save path if it's not defined in the config. Example: If you manually download a torrent and it's saved in /data/torrents/Movies and your config.yml doesn't have a Movie category it will automatically add the Movie category in your config for you.

In terms of file pattern, not sure if that's really feasible because what if there are multiple files in the torrent? What if multiple categories match with the rules you set?

@leo-carmo
Copy link

Too bad the idea on #5779 is not coming through, at least apparently :(

@bobokun bobokun added the status:more-info-needed More information is needed label Jan 1, 2022
@bobokun bobokun added the status:unlikely FR that are not out of scope for qbm label Jan 14, 2022
@bobokun bobokun closed this as not planned Won't fix, can't repro, duplicate, stale Aug 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New feature or request status:more-info-needed More information is needed status:unlikely FR that are not out of scope for qbm
Projects
None yet
Development

No branches or pull requests

3 participants