Gusted be6416e990 [GITEA] Fix /issues/search endpoint ... - The endpoint was moved from being an API endpoint to an web endpoint with JSON result. However the API context isn't the same as the web context, for example the `ctx.Error` only takes in the first two arguments into consideration and doesn't do logging, which is not the same behavior as the API context where there's three arguments and does do logging and only reveal the function + error if the user is admin. - Remove any details in the error message and do the logging seperatly, this is somewhat consistent with how other API endpoints behave. - Ref: https://codeberg.org/forgejo/forgejo/issues/1998 (cherry picked from commit fe71e32ace) (cherry picked from commit c89e0735fa) (cherry picked from commit 4c04dcfc59) (cherry picked from commit 66eae1041c) (cherry picked from commit 7b70fa9392) (cherry picked from commit abf64ca0e3)		2024-02-05 16:09:42 +01:00
..
actions
setting
activity.go
attachment.go
blame.go
branch.go
cherry_pick.go
commit.go
compare.go
download.go
editor.go
editor_test.go
find.go
githttp.go
githttp_test.go
helper.go
helper_test.go
issue.go
issue_content_history.go
issue_dependency.go
issue_label.go
issue_label_test.go
issue_lock.go
issue_pin.go
issue_stopwatch.go
issue_test.go
issue_timetrack.go
issue_watch.go
main_test.go
middlewares.go
migrate.go
milestone.go
packages.go
patch.go
projects.go
projects_test.go
pull.go	Simplify how git repositories are opened (#28937)	2024-01-27 21:09:51 +01:00
pull_review.go
release.go
release_test.go
render.go
repo.go
search.go
topic.go
treelist.go
view.go
view_test.go
wiki.go
wiki_test.go