summaryrefslogtreecommitdiff
path: root/issues
diff options
context:
space:
mode:
authorArun Isaac2023-02-15 16:50:53 +0000
committerArun Isaac2023-02-15 16:52:00 +0000
commita5193b8829b0b87352bc61c5892df3579b526bbc (patch)
tree0fbcd184ebd985168f48845bf39567221f2723ba /issues
parentea9b2f14836158def6c524152c77c542124f428a (diff)
downloadgn-gemtext-a5193b8829b0b87352bc61c5892df3579b526bbc.tar.gz
Report invalid search queries over API.
Diffstat (limited to 'issues')
-rw-r--r--issues/report-invalid-search-queries-over-api.gmi8
1 files changed, 8 insertions, 0 deletions
diff --git a/issues/report-invalid-search-queries-over-api.gmi b/issues/report-invalid-search-queries-over-api.gmi
new file mode 100644
index 0000000..f61fbfe
--- /dev/null
+++ b/issues/report-invalid-search-queries-over-api.gmi
@@ -0,0 +1,8 @@
+# Report invalid search queries passed to the search API
+
+* assigned: alex, arun
+* tags: enhancement
+
+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.