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

Add ability for youtube channel seasons and episode order be specified by filename date #284

Merged
merged 4 commits into from
Jun 14, 2020

Conversation

tjw1184
Copy link
Contributor

@tjw1184 tjw1184 commented Jun 14, 2020

Currently for youtube channels (UC) the seasons and episode order are set\ordered by file modification date. On my system I have numerous files where the modification date is wrong for one reason or another and episodes are in the wrong seasons or in the wrong order.

When downloading the channel, I begin all filenames with yyyymmdd - * so the information to order the files is already in the filename. I modified the scanner to order files by filename and then extract the season from the date in the filename.

Other than the sorting change, I believe all other edits should be transparent to users that don't follow this naming convention - but to ensure it wouldn't affect users unintentionally I tied the new behavior to an option boolean and defaulted it to off. As I know some start their filenames in a similar way with date first I figured others could benefit from this change.

Order files by filename, if filename starts with yyyy-mm-dd then extract first four characters as season number
Fix whitespace issues.  Modified regex to allow starting date formats of "yyyy-mm-dd" "yyyy.mm.dd" "yyyy mm dd" and "yyyymmdd"
@ZeroQI ZeroQI merged commit 861e3d1 into ZeroQI:master Jun 14, 2020
EndOfLine369 added a commit that referenced this pull request Aug 8, 2020
@EndOfLine369
Copy link
Collaborator

FYI, b610fe8

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants