Fix TVDB plugin not handling absolute display order #4054
Merged
Conversation
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
|
Example: With fix it is correctly displayed as episode 58: |
cvium
approved these changes
Sep 5, 2020
Bond-009
approved these changes
Sep 5, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
Add check for "absolute" order and set IndexNumber to TVDBs AbsoluteNumber.
From what I've seen AbsoluteNumber can be either null or 0 on TVDB, both should be considered invalid (there are some shows where all episodes have their absolute number set to 0). I think in that case the best action is to leave it at the default id.IndexNumber that Jellyfin presumably got from parsing the filename.
Issues
addresses #3062