Kemal Zebari 9b7af4340c 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.		2024-04-23 15:10:01 +08:00
..
bleve	Determine fuzziness of bleve indexer by keyword length (#29706)	2024-03-23 16:45:13 +01: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-24 18:51:08 +00:00
elasticsearch	Enable more revive linter rules (#30608)	2024-04-22 11:48:42 +00:00
internal	Use db.ListOptions directly instead of Paginator interface to make it easier to use and fix performance of /pulls and /issues (#29990)	2024-03-24 18:51:08 +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-24 18:51:08 +00:00
dboptions.go	Perform Newest sort type correctly when sorting issues (#30644)	2024-04-23 15:10:01 +08:00
indexer_test.go
indexer.go	Use db.ListOptions directly instead of Paginator interface to make it easier to use and fix performance of /pulls and /issues (#29990)	2024-03-24 18:51:08 +00:00
util.go