Save the episodes fetched for Recently Released Shows

Closed
  • Is something wrong?
#60 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
kotlin
Domain
mobile

Research direction

Read issue #59 and the Home sync path that performs the recently released air-date step, then trace get_series_info and ensureEpisodes to see where fetched episodes can be saved and found. The change is on hold pending a decision about whether opening a series from Home is slow on Fire TV Stick. Done means those episodes are available without a network call, saving cannot disrupt or slow sync, other series remain lazy, and docs/ARCHITECTURE.md records the exception.

Written by the indexing model from the issue text.

Description

needs-triage

Parent

neutraltone/settee#1

Blocked by #59 (the recently-released Home rows).

What to build

The Home "Recently Released Shows" step calls get_series_info for the ~50 most recently updated series after each sync, but only keeps the latest air date. Saving the episodes it already fetched would make opening those series instant, since they're the ones most likely to be opened.

On hold: only worth doing if opening a series from Home feels slow on the Fire TV Stick. This loosens the "episodes are fetched lazily" rule, so it needs a decision before it's built.

Acceptance criteria

  • Episodes returned by the background air-date step are saved, so ensureEpisodes finds them without a network call
  • Saving them never fails or slows the catalogue sync, and every other series still loads its episodes lazily
  • docs/ARCHITECTURE.md notes the exception to lazy episode loading
Dominant language
Kotlin
Stars
0
Forks
0
Avg merge
2h 15m
Merged PRs (30d)
68

Getting set up

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.

More from neutraltone/settee

All issues in neutraltone/settee

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.