summaryrefslogtreecommitdiff
path: root/issues/report-invalid-search-queries-over-api.gmi
diff options
context:
space:
mode:
authorAlexander_Kabui2023-04-04 03:57:46 +0300
committerAlexander_Kabui2023-04-04 03:57:46 +0300
commitb5b4cad076adf907af436867798d40f4ac66e92a (patch)
tree1883fb8c6bb18c187307e52c3add97f8ebb5b38e /issues/report-invalid-search-queries-over-api.gmi
parent739b4e6c80fab18f72145a7fa8a91016c10e9f0d (diff)
downloadgn-gemtext-b5b4cad076adf907af436867798d40f4ac66e92a.tar.gz
update search issues
Diffstat (limited to 'issues/report-invalid-search-queries-over-api.gmi')
-rw-r--r--issues/report-invalid-search-queries-over-api.gmi6
1 files changed, 6 insertions, 0 deletions
diff --git a/issues/report-invalid-search-queries-over-api.gmi b/issues/report-invalid-search-queries-over-api.gmi
index f61fbfe..1efa0ab 100644
--- a/issues/report-invalid-search-queries-over-api.gmi
+++ b/issues/report-invalid-search-queries-over-api.gmi
@@ -1,8 +1,14 @@
+
+
# Report invalid search queries passed to the search API
* assigned: alex, arun
* tags: enhancement
+* status: in progress
+
+
+
genenetwork2 offloads search to the genenetwork3 search API. When there is an error in the genenetwork3 API call, genenetwork2 has no idea what went wrong and cannot produce a good stacktrace. The genenetwork3 API should do a better job of communicating errors.
In particular, for the search API, we should start with correctly reporting invalid search queries so that genenetwork2 can present it appropriately in its web UI.