forgejo/models/user
wxiaoguang 459ee98136
Only use supported sort order for "explore/users" page (#29430)
Thanks to inferenceus : some sort orders on the "explore/users" page
could list users by their lastlogintime/updatetime.

It leaks user's activity unintentionally. This PR makes that page only
use "supported" sort orders.

Removing the "sort orders" could also be a good solution, while IMO at
the moment keeping the "create time" and "name" orders is also fine, in
case some users would like to find a target user in the search result,
the "sort order" might help.

![image](https://github.com/go-gitea/gitea/assets/2114189/ce5c39c1-1e86-484a-80c3-33cac6419af8)

(cherry picked from commit eedb8f41297c343d6073a7bab46e4df6ee297a90)
2024-03-06 12:10:43 +08:00
..
avatar.go
badge.go
block.go [MODERATION] User blocking 2024-02-05 15:56:45 +01:00
block_test.go [MODERATION] User blocking 2024-02-05 15:56:45 +01:00
email_address.go [GITEA] Allow changing the email address before activation (squash) 2024-02-05 16:57:58 +01:00
email_address_test.go [GITEA] Allow changing the email address before activation (squash) 2024-02-05 16:57:58 +01:00
error.go Remove unused KeyID. (#29167) 2024-02-16 15:20:52 +01:00
external_login_user.go Remove GetByBean method because sometimes it's danger when query condition parameter is zero and also introduce new generic methods (#28220) 2023-12-07 15:27:36 +08:00
follow.go [MODERATION] User blocking 2024-02-05 15:56:45 +01:00
follow_test.go
list.go
main_test.go
must_change_password.go
openid.go
openid_test.go
redirect.go
redirect_test.go
search.go Only use supported sort order for "explore/users" page (#29430) 2024-03-06 12:10:43 +08:00
setting.go
setting_keys.go
setting_test.go
user.go Start to migrate from util.OptionalBool to optional.Option[bool] (#29329) 2024-02-26 22:30:26 +01:00
user_system.go [BRANDING] reserve forgejo-actions username 2024-02-05 16:05:01 +01:00
user_test.go Allow non-admin users to delete review requests (#29057) 2024-02-26 22:30:27 +01:00
user_update.go