fix(frontend): use search param for pool "add files" name search
The add-files search built a {n~%text%} filter token, but the filter DSL
only supports t=, m= and m~, so the backend rejected it as an unknown token
and no results appeared. Use the search query param (ILIKE on name) instead.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
@@ -291,7 +291,7 @@
|
|||||||
try {
|
try {
|
||||||
const params = new URLSearchParams({ limit: String(LIMIT), sort: 'created', order: 'desc' });
|
const params = new URLSearchParams({ limit: String(LIMIT), sort: 'created', order: 'desc' });
|
||||||
if (addNextCursor) params.set('cursor', addNextCursor);
|
if (addNextCursor) params.set('cursor', addNextCursor);
|
||||||
if (addSearch.trim()) params.set('filter', `{n~%${addSearch.trim()}%}`);
|
if (addSearch.trim()) params.set('search', addSearch.trim());
|
||||||
const res = await api.get<FileCursorPage>(`/files?${params}`);
|
const res = await api.get<FileCursorPage>(`/files?${params}`);
|
||||||
addFiles = [...addFiles, ...(res.items ?? [])];
|
addFiles = [...addFiles, ...(res.items ?? [])];
|
||||||
addNextCursor = res.next_cursor ?? null;
|
addNextCursor = res.next_cursor ?? null;
|
||||||
|
|||||||
Reference in New Issue
Block a user