recloudstream / recloudstream/cloudstream

Filler & metadata-sync matching by episode number breaks for providers with non-canonical numbering (regional editions)

Open
#3,166 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Kotlin
Stars
10.7k
Forks
1.1k
Avg merge
1d 23h
Merged PRs (30d)
15

Description

Describe your suggested feature

FillerEpisodeCheck.getFillerEpisodes() returns canonical (animefillerlist) episode numbers, and ResultViewModel2 flags fillers with fillers.contains(i.episode ?: index + 1). The same number-keyed matching drives Kitsu/AniList episode metadata (this.name = this.name ?: node.titles?.canonical, keyed by this.episode).

This breaks for providers that legitimately expose a regional edition whose numbering diverges from the canonical MAL/AniList one. Concrete case: the Italian edition of Detective Conan (AnimeUnity) is renumbered, and occasionally one Japanese episode is split into two (IT ep 53 + 54 = JP ep 52). Result: fillers marked on the wrong episodes, synced titles/thumbnails on the wrong episodes.

Other details

No response

Acknowledgements
  • My suggestion is NOT about adding a new provider
  • I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing FillerEpisodeCheck.getFillerEpisodes() into ResultViewModel2, then inspect the Kitsu/AniList metadata matching keyed by episode. The issue does not name files or tests; done would require a defined mapping that keeps fillers, titles, and thumbnails aligned for regional and split episode numbering.

Written by the indexing model from the issue text.

Assessment

Tech stack
kotlin
Domain
mobile-dev
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.