Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
torznab: add support for languages and subtitles
- Loading branch information
1 parent
9638823
commit 04e24ba
Showing
3 changed files
with
11 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
04e24ba
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want to add this to cardigann as well?
Bump to v0.21.* for this?
04e24ba
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, sadly only AvistaZ properly supports this. I'm all for adding it to Cardigann, but I don't think we are there yet.
Yeah, it's been 0.20.x for too long. π
04e24ba
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only just checking this now; I didn't realise that each
language
orsubs
is separate, e.g.:rather than a list, like
genre
, e.g.:Had I taken more than a cursory glance at the code, that would have been obvious, but π€·.
Would
genre
be better off like this as well? Or for that matter, would it be better forlanguage
andsubs
to be a list?As far as I'm aware, nothing uses
genre
yet, so if we were to change it, now would probably be the best time.04e24ba
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I already talked with Q on this topic (list vs string with comma), and we came to the conclusion that the spec isn't really definitive on this regard. Sonarr and Radarr already parses multiple occurrences of
language
, so let's leave it as list.I would leave
Genres
as is, the spec has it with example as string separated by comma.