Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add sort-options to the search-inside API #4997

Open
waldenn opened this issue Apr 7, 2021 · 1 comment
Open

add sort-options to the search-inside API #4997

waldenn opened this issue Apr 7, 2021 · 1 comment
Labels
Lead: @mekarpeles Issues overseen by Mek (Staff: Program Lead) [managed] Priority: 4 An issue, but should be worked on when no other pressing work can be done. [managed]

Comments

@waldenn
Copy link

waldenn commented Apr 7, 2021

Describe the problem that you'd like solved

The search-inside API currently has no way to sort the results, which is possible in the search API.

Note: sorting is also not yet possible in the search-inside web interface:

Proposal & Constraints

I would like to see some basic sort-options for the inside-search API (and ideally also the web interface).

The most important options (in my opinion):

  • sort by number of matches (the current default perhaps?).
  • sort by relevance: which would also take into account title-matches etc. (besides the number of matches within an item), like this is done for the search API.

Other "nice to have" options would be:

  • new (newest first)
  • old (oldest first)
  • author asc
  • auther desc
  • title asc
  • title desc
  • month/week views asc
  • month/week views desc
@waldenn waldenn added Needs: Lead Needs: Triage This issue needs triage. The team needs to decide who should own it, what to do, by when. [managed] labels Apr 7, 2021
@waldenn waldenn changed the title add some important sort-options for search-inside API add sort-options to the search-inside API Apr 7, 2021
@Priyanshujha11
Copy link

assign this to me

@mekarpeles mekarpeles added Priority: 4 An issue, but should be worked on when no other pressing work can be done. [managed] Lead: @mekarpeles Issues overseen by Mek (Staff: Program Lead) [managed] and removed Needs: Lead Needs: Triage This issue needs triage. The team needs to decide who should own it, what to do, by when. [managed] labels Apr 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Lead: @mekarpeles Issues overseen by Mek (Staff: Program Lead) [managed] Priority: 4 An issue, but should be worked on when no other pressing work can be done. [managed]
Projects
None yet
Development

No branches or pull requests

3 participants