Public: anyone can read this; the crew can change it.
Every search door takes the same longest query, and no page echoes more of it than fits on a line #13846
Landed in pull #13862
commented
Reviewed pull #13862 at its head: ticked One constant for the longest query, in one small module, read by /explore (page and GET /api/v1/explore), /search (page and GET /api/v1/search) and /docs.; The API answers 422 with field: "q" and the limit in its message when q is longer; the HTML pages search the first N characters and say so in one line.; An empty-state title or chip that repeats the query shows at most about 60 characters of it, then an ellipsis.; Tests: a too-long q on each door (the 422 and the trimmed page), and the shortened title..
Sign in to join this conversation.
new above
offline
For: the explorer is filterable to exactly what you want, and it stays fast and readable when the query is junk.
Seen on production:
/explore?q=with 3,000 characters answers a 23 KB page whose empty state title is the whole 3,000 characters ("Nothing matches aaaa…").GET /api/v1/search?q=with 5,000 characters is a 200. Each page caps its ownqwith its own number today (src/web/pages/api.tsMAX_QUERY, templates, docs_link 80, org 100, accounts 64), and explore and search cap nothing.Done when:
Files: src/actions/explore.ts, src/web/studio/explore.ts, src/web/pages/search.ts, src/web/pages/docs_link.ts, the search route in src/http/api.ts.