forgejo/modules/indexer/issues
Kemal Zebari 50917ead5f
Perform Newest sort type correctly when sorting issues (#30644)
Should resolve #30642.

Before this commit, we were treating an empty `?sort=` query parameter
as the correct sorting type (which is to sort issues in descending order
by their created UNIX time). But when we perform `sort=latest`, we did
not include this as a type so we would sort by the most recently updated
when reaching the `default` switch statement block.

This commit fixes this by considering the empty string, "latest", and
just any other string that is not mentioned in the switch statement as
sorting by newest.

(cherry picked from commit 9b7af4340c36d3e1888788499d16f83feeb1601b)
2024-04-28 15:39:00 +02:00
..
bleve [FIX] Set max fuzziness to 2 for bleve (#3444) 2024-04-26 08:08:47 +00:00
db Use db.ListOptions directly instead of Paginator interface to make it easier to use and fix performance of /pulls and /issues (#29990) 2024-03-30 07:17:29 +01:00
elasticsearch Enable more revive linter rules (#30608) 2024-04-28 15:39:00 +02:00
internal [FIX] Set max fuzziness to 2 for bleve (#3444) 2024-04-26 08:08:47 +00:00
meilisearch Use db.ListOptions directly instead of Paginator interface to make it easier to use and fix performance of /pulls and /issues (#29990) 2024-03-30 07:17:29 +01:00
dboptions.go Perform Newest sort type correctly when sorting issues (#30644) 2024-04-28 15:39:00 +02:00
indexer.go s/Gitea/Forgejo in various log messages and comments 2024-04-21 21:26:15 +05:00
indexer_test.go Refactor to use optional.Option for issue index search option (#29739) 2024-03-20 08:46:28 +01:00
util.go Use db.ListOptionsAll instead of db.ListOptions{ListAll: true} (#29995) 2024-03-26 19:04:27 +01:00