gitea

Commit Graph

Author	SHA1	Message	Date
wxiaoguang	4c476fa41d	Remove unnecessary ".Link" usages (#29909 ) In HTML, `?key=val` already means "use the current link with new query parameters"	8 months ago
wxiaoguang	eedb8f4129	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)	9 months ago

Author

SHA1

Message

Date

wxiaoguang

4c476fa41d

Remove unnecessary ".Link" usages (#29909 )

In HTML, `?key=val` already means "use the current link with new query parameters"

8 months ago

wxiaoguang

eedb8f4129

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)

9 months ago

2 Commits (89cc5011716850eb30c9e34130c4b2ecd9829252)