Skip to content

sync: add the parental guide filters to get_up_next_nitro - #322

Merged
mfederowicz merged 1 commit into
mainfrom
sync-up-next-nitro-parental
Oct 31, 2026
Merged

mfederowicz merged 1 commit into
mainfrom
sync-up-next-nitro-parental

Conversation

@mfederowicz

Copy link
Copy Markdown
Owner

Added

  • sync -a get_up_next_nitro takes the parental guide filters: -parental_nudity, -parental_violence, -parental_profanity, -parental_alcohol and -parental_frightening, each a range min-max from 0 to 3, and -parental_include_unrated.
  • Library: uri.UpNextNitroOptions gets the six Parental* fields.

This is the follow-up to #321. The contract (trakt-api 719eef7) gives sync/progress/up_next_nitro the same filters. It reuses parentalFilterFlags and the shared checkParentalRanges, so a bad range stops before any request. The live check on 2026-10-31 covered movies|shows/popular; this route is mock-tested.

An AI assistant (Claude Code) wrote the change, the tests and the docs, and drafted this description.

The contract (trakt-api 719eef7) gives sync/progress/up_next_nitro the same parental_* filters
as the other media filter routes (#321). Reuses parentalFilterFlags and checkParentalRanges.
@mfederowicz
mfederowicz merged commit b910555 into main Oct 31, 2026
6 checks passed
@mfederowicz
mfederowicz deleted the sync-up-next-nitro-parental branch October 31, 2026 01:45
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.

1 participant