fix(snippets): remove playlist gradient

[RielieSimpson]

Remove Top gradient lost some functionality, added a piece to bring functionality back. Specifically, it stopped removing gradients on playlists.

Summary by CodeRabbit

• New Features
  • Expanded the “Remove Top gradient” snippet to also hide the gradient bar on playlist pages, providing a cleaner, distraction-free header area across more views.
  • Ensures a more consistent look by removing the playlist action bar gradient along with the top gradient previously removed.
  • Improves visual clarity for users who prefer a minimal interface.

[coderabbitai]

Walkthrough

Added a CSS selector to the "Remove Top gradient" snippet in resources/snippets.json to also hide the playlist action bar gradient background by setting it to display: none.

Changes

Cohort / File(s)	Summary
Snippets configuration resources/snippets.json	Updated the "Remove Top gradient" snippet to include the selector .playlist-playlist-actionBarBackground-background alongside existing selectors set to display: none.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I nibbled code like clover sprigs,
Trimmed a gradient’s lofty wigs—
One more bar now fades from sight,
Sleek as moon on playlist night.
Thump-thump! My paws approve the scene,
CSS tidy, crisp, and clean.

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.
Title Check	✅ Passed	The title “fix(snippets): remove playlist gradient” accurately captures the core change of the pull request, which is to hide the playlist gradient bar by updating the snippet selectors, and it is concise and specific without any extraneous details.

✨ Finishing touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

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 and usage tips.}