Repository navigation
Use calendar year instead of ISO week year for the file date - #1989
Merged
Merged
Conversation
Member
|
Great catch |
This file contains hidden or 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
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.
Use
%Yinstead of%Gwhen storingfile_dtlin themotiontable so the date uses the calendar year.%Gformats the ISO 8601 week-based year, which can differ from the calendar year near New Year. For example, a file recorded on 2027-01-01 would be stored as20260101, and a file recorded on 2025-12-29 would be stored as20261229.cls_schedule::cleandir_sql()comparesfile_dtlwith a date built from the calendar year. This mismatch can cause recordings to be deleted prematurely or retained for roughly a year longer than intended. The value also determines file-list ordering and is exposed asdateinmovies.json.