Add chapter timestamps to Reset Scans

[StudentSerai1181201811]

Source name

Reset Scans

Source language

"English"

Describe your suggested feature

What I like to do in my library is sort entries by latest update so that I know which entries only recently updated new chapters. This is especially useful for large libraries and backlogs and prioritizing entries that are already caught up first. This kind of breaks for entries with no dateTime with their chapters.

Currently, dates for chapters an entry on the website are like so:

<span class="chapter-release-date">
    <i>31-Mar</i>
</span>

Formatted as dd-MMM

So what can be done is fetching the date string using the class name and then formatting it as datetime. Years aren't included in the string so we'll be using the current year instead.

Other details

Obviously, the date not including a year is a problem especially for entries with chapters that were released before 2025.

As an example, we'll look at this entry.

Earliest chapter for 2025 is "01-Jan" but when we get to the 2024 chapters, it's still the same format at "26-Dec".

Fixing this, I assume could be done like this: Iterate chapters from top to bottom from source sorting. Parse chapter date with previous iteration with the current set year. If current iteration chapter date is larger than previous iteration, set year to year - 1, and reparse chapter date with new year.

This does kind of break under 2 situations:

• If an entry has a year gap of updates, it will mislabel a 2023 chapter as 2024
• If an entry has a missing chapter and is then uploaded at a date later than it's succeeding chapter. ie. Chapter 75: 25-Mar, Chapter 74: 27-Mar, Chapter 73: 12-Mar; This will mislabel 74 and any preceding chapter as 2024 until the 2024 chapters which will then be mislabelled as 2023.

However, since the point of this is to get the date for the latest chapter of an entry for library sorting, this kind of break is not that important

Acknowledgements

• [x] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
• [x] I have written a short but informative title.
• [x] If this is an issue with the app itself, I should be opening an issue in the app repository.
• [x] I have updated the app to version 0.15.3.
• [x] I will fill out all of the requested information in this form.

---

Add a :+1: reaction to issues you find important.

[vetleledaal]

See https://github.com/keiyoushi/extensions-source/issues/7519#issuecomment-2657232351:

This is not really an issue with the extension. Guesstimating the year is in my opinion not a valid solution.

The date not being recognized is however a bug.