From 783a02188970ba5800514f7c64f6a818f65c04a1 Mon Sep 17 00:00:00 2001 From: Lunny Xiao Date: Fri, 8 Apr 2022 02:59:56 +0800 Subject: Never use /api/v1 from Gitea UI Pages (#19318) Reusing `/api/v1` from Gitea UI Pages have pros and cons. Pros: 1) Less code copy Cons: 1) API/v1 have to support shared session with page requests. 2) You need to consider for each other when you want to change something about api/v1 or page. This PR moves all dependencies to API/v1 from UI Pages. Partially replace #16052 --- web_src/js/features/comp/SearchUserBox.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'web_src/js/features/comp') diff --git a/web_src/js/features/comp/SearchUserBox.js b/web_src/js/features/comp/SearchUserBox.js index 18b67919b5..08f97595af 100644 --- a/web_src/js/features/comp/SearchUserBox.js +++ b/web_src/js/features/comp/SearchUserBox.js @@ -8,7 +8,7 @@ export function initCompSearchUserBox() { $searchUserBox.search({ minCharacters: 2, apiSettings: { - url: `${appSubUrl}/api/v1/users/search?q={query}`, + url: `${appSubUrl}/user/search?q={query}`, onResponse(response) { const items = []; const searchQueryUppercase = $searchUserBox.find('input').val().toUpperCase(); -- cgit v1.2.3