[britsync07-prog]

Description

• Fixes hideAvailable/hideBlocklisted discover filters drop non-movie/tv results #3433

When hideAvailable or hideBlocklisted filter options are enabled, useDiscover and MediaSlider were filtering all items whose media type had no media status (such as Person search results), causing them to disappear from the slider. This fix ensures availability and blocklist filters only apply to Movie and TV items, allowing non-media results (e.g. Person cards) to display properly.

AI Disclosure: I researched the filtering logic in useDiscover and MediaSlider and implemented the type guard checks manually to prevent filtering non-media items.

How Has This Been Tested?

Tested the changes against the discover view and media slider endpoints:

• Verified that when hideAvailable or hideBlocklisted is active, Person search results remain visible in discovery sliders.
• Verified that Movies and TV shows with available or blocklisted status continue to be filtered as expected.
• Ran unit test suite (pnpm test) and verified local build (pnpm build).

Screenshots / Logs (if applicable)

N/A

Checklist:

• I have read and followed the contribution guidelines.
• Disclosed any use of AI (see our policy)
• I have updated the documentation accordingly.
• All new and existing tests passed.
• Successful build pnpm build
• Translation keys pnpm i18n:extract
• Database migration (if required)

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 3594fb7e-7aaf-4bcf-910e-7d5d8d078eaa

📥 Commits

Reviewing files that changed from the base of the PR and between 92f8404 and c422fea.

📒 Files selected for processing (2)

• src/components/MediaSlider/index.tsx
• src/hooks/useDiscover.ts

Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review.

---

📝 Walkthrough

Walkthrough

The change updates availability and blocklist filtering in MediaSlider and useDiscover. Movie and TV results remain subject to status filters. Non-movie and non-TV results, including people, remain visible.

Changes

Discover filtering

Layer / File(s)	Summary
Guard media status filters src/components/MediaSlider/index.tsx, src/hooks/useDiscover.ts	Availability and blocklist filters now preserve non-movie and non-TV results. Movie and TV results continue to be filtered by their respective statuses.

Estimated code review effort: 2 (Simple) | ~10 minutes

Merge Risk: ⚪ Minimal · up to c422f

This localized filter correction is merge-ready after normal checks and review; no actionable merge-blocking risk remains.

Suggested reviewers: 0xsysr3ll, danshilm

Poem

A rabbit checked the movie queue
And kept the people in view
TV flags still guide the way
Blocklists trim what should not stay
Non-media friends remain there too

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	The changes in useDiscover and MediaSlider satisfy issue #3433 by applying availability and blocklist filters only to movie and TV results while preserving non-movie/tv results.
Out of Scope Changes check	✅ Passed	The changes are limited to the filtering behavior described in issue #3433 and the pull request objectives. No unrelated changes are shown.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: preventing hideAvailable and hideBlocklisted from filtering person results.

✨ Finishing Touches 💡 1

🛠️ Fix failing CI checks 💡

• Create stacked PR
• Commit on current branch

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[fallenbagel]

@britsync07-prog Please fill the template properly. Do not check stuff that are not relevant to this PR. There is no database migrations, no documentation, no translation keys in this PR to have those checked.

In addition, please read the contributing guidelines before you submit a PR. The checkbox is ticked but the disclosure is left blank. That is mandatory in accordance to our contributing guidelines. That field needs an actual answer. Simply ticking it does not follow our contributing guidelines. This applies to the PR descriptions too. See here:

seerr/CONTRIBUTING.md

Lines 28 to 46 in 92f8404

	### Disclosure Requirements
	If you are using any kind of AI assistance while contributing to Seerr, **this must be disclosed in the pull request description**, along with the extent to which AI assistance was used (e.g., docs only vs. code generation).
	PR responses (comments, review replies) must be written in your own words, per the Expectations below. The one exception is AI-assisted translation, if you use AI to translate a response into English, disclose that here too.
	As a small exception, trivial tab-completion doesn't need to be disclosed, so long as it is limited to single keywords or short phrases.
	**Disclosure does not exempt a PR from the AI-driven development policy above.**
	If the implementation was primarily generated by an AI tool in one or two prompts, and your own involvement was limited to testing or a small edit, that is AI-driven development whether or not you disclosed it. Disclosure tells us how much scrutiny to apply to your PR. It does not turn an AI-driven contribution into an AI-assisted one.
	Example disclosures that meet our bar:
	> - **AI Disclosure:** I designed the approach and wrote the implementation myself.
	> I used Claude to scaffold the initial component and help debug a TypeScript
	> generics issue.
	> - **AI Disclosure:** I consulted ChatGPT to understand the codebase but the solution
	> was fully authored manually by myself.
	> - **AI Disclosure:** None.

Update the description with that so we could proceed with further review.

[britsync07-prog]

@fallenbagel Thank you for the feedback! I've updated the PR description following the template accurately, included the AI disclosure, and unchecked items not relevant to this change (docs, translations, database migrations).