Feat/watchlist sorting

[seferturan]

🎶 Notes 🎶

• Fixes Add sorting support to watchlist page #1479
• Adds support to sorting watch list items.
  • ⚠️ The direction seems to be reversed. I left a fixme in there to pick up when fixed in backend
    • This is now fixed in the API.

👀 Example 👀

Screen.Recording.2026-01-23.at.12.57.50.mov

[gemini-code-assist]

Summary of Changes

Hello @seferturan, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request delivers a significant enhancement by enabling sorting capabilities for watchlist items, directly addressing issue #1479. The changes encompass an update to the Trakt API client, a comprehensive refactoring of watchlist data fetching parameters to support explicit sorting criteria, and the integration of new UI components to allow users to interact with these sorting options. The update also includes improvements to URL generation for various list types, ensuring consistent navigation and state management. A temporary fix for a reversed sort direction from the backend is in place, marked for future resolution.

Highlights

• Watchlist Sorting Implementation: Introduced the functionality to sort items within a user's watchlist, allowing users to organize their watchlists based on various criteria.
• Trakt API Client Update: Updated the @jsr/trakt__api dependency from version 0.3.0 to 0.3.2, ensuring the client uses the latest API features and fixes.
• Refactored Watchlist Query Parameters: The watchlistQuery now utilizes sortBy and sortHow parameters instead of a single sort parameter, providing more granular control over sorting direction.
• Enhanced URL Generation for Lists: The getListUrl utility has been refactored to support both user-defined lists and watchlists, and can now incorporate sorting parameters directly into the generated URLs.
• Dynamic Sorting UI Integration: Integrated sorting actions into the WatchlistPaginatedList.svelte and UserListPaginatedList.svelte components, providing a user interface for selecting sorting options.
• Temporary Sort Direction Inversion: A FIXME comment and corresponding logic have been added to temporarily invert the sort direction for watchlist items, addressing a potential discrepancy with the backend API's sorting behavior.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[deepsource-io]

Here's the code health analysis summary for commits 8366989..5a9d104. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
JavaScript	✅ Success		View Check ↗
Test coverage	✅ Success		View Check ↗

Code Coverage Report

Metric	Aggregate	Javascript
Branch Coverage	25%	25%
Composite Coverage	27.5%	27.5%
Line Coverage	28.6%	28.6%

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[gemini-code-assist]

Code Review

This pull request introduces sorting functionality for watchlist items, addressing issue #1479. It involves significant refactoring of URL generation and sorting logic across several Svelte components and utility functions. The changes are generally well-structured and adhere to the repository's naming conventions and TypeScript standards. A FIXME comment highlights a known issue with the backend regarding sort direction, which is temporarily handled in the frontend. All original comments have been retained as they do not contradict any provided rules.

[CanePlayz]

@seferturan You might already be aware of that, but that inverse direction problem happens on all lists if I'm not mistaken

[seferturan]

@CanePlayz, that was indeed an issue, but in v3 the list items should be sorted in the correct direction.

[seferturan]

Drafting this for now until backend sorting is changed.

[CanePlayz]

@CanePlayz, that was indeed an issue, but in v3 the list items should be sorted in the correct direction.

I see what my issue is. When opening a list in v3, the defined sorting direction is just not reflected properly.

[seferturan]

@CanePlayz, that's due to v2 inverting the sort setting 😅 In the list settings it seems to be set to desc. As a workaround for now, you can change the default sorting to be ascending.

[CanePlayz]

@CanePlayz, that's due to v2 inverting the sort setting 😅 In the list settings it seems to be set to desc. As a workaround for now, you can change the default sorting to be ascending.

@seferturan Sorry for having to ask again, I'm just a bit lost on this issue.

It seems to be set to ascending in the list settings.

And v2 sorts ascending. v3 doesn't.

Edit: Ohh, was that related to the API issue and will be fixed soon?