Skip to content

Sort issues from a menu in the table header - #10

Open
NoSync wants to merge 1 commit into
ajma:mainfrom
Klartika:feat/sort-issues
Open

NoSync wants to merge 1 commit into
ajma:mainfrom
Klartika:feat/sort-issues

Conversation

@NoSync

@NoSync NoSync commented Oct 22, 2026

Copy link
Copy Markdown

Closes #4.

Adds a sort menu at the end of the issue table's header, after the filter menus, as on github.com. It offers GitHub's orders: Newest, Oldest, Recently updated, Least recently updated, Most commented and Most reactions. The button names the current order.

  • The choice is saved with the other per-host settings (sort, defaulting to created-desc), so it carries across sessions and clients like the density.
  • issues.page takes an optional sort and passes it to the search API as sort/order, which were fixed to created/desc. Changing the order goes back to page 1.
  • The sort menu reuses the filter dropdown (a sheet on compact and native layouts) without the search box. Each menu now starts with an empty search, so text typed in one menu does not filter the next.
  • README, OVERVIEW and CLAUDE.md mention the menu.

Tested: npm run typecheck and npm test (new server, shared and screen tests). Also installed on a Paseo host and called issues.page through the daemon with several orders, checking the results against gh api search/issues with the same parameters.

🤖 Generated with Claude Code

The sort menu offers GitHub's orders: newest, oldest, recently updated,
least recently updated, most commented and most reactions. The choice is
saved with the other host settings and passed to the search API as its
sort and order parameters, which were fixed to created/desc.

Closes ajma#4

Co-Authored-By: Claude Opus 5.5 <[email protected]>
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.

Support sort order and sort by

1 participant