Let the search reach past the twentieth of a kind, and unbreak two specs
The global search capped each category before cmdk had matched anything, so nothing past the twentieth node or widget could be found at all — this instance has 28 nodes and 97 widgets. The cap now trims the candidates the query could reach rather than the raw index. The admin teardown asked /users/ for limit=1000, which the route stopped accepting when its bounds went in; a 422 body has no `data` to iterate, so the hook threw and took the tests it was attributed to with it. It asks for the 500 the route allows. And `submit` folds every declared initial into a run's params, so an input the run never passed can no longer read as the flow's own. That assertion is gone; what the panel does show — the value the run actually started from, passed or not — is what the test checks. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CL9zvnnvcp1mvA8o7impxk
This commit is contained in:
@@ -10,7 +10,9 @@ test.afterAll(async ({ browser }) => {
|
||||
// sweep them all up by that shape — including what a run that failed halfway
|
||||
// left in the shared development database.
|
||||
const page = await apiPage(browser)
|
||||
const { data } = await (await api(page, "/users/?limit=1000")).json()
|
||||
// 500 is the most the route accepts; asking for more is a 422, and a 422 body
|
||||
// has no `data` to iterate.
|
||||
const { data } = await (await api(page, "/users/?limit=500")).json()
|
||||
for (const user of data as { id: string; email: string }[]) {
|
||||
if (/^test_.*@example\.com$/.test(user.email)) {
|
||||
await api(page, `/users/${user.id}`, { method: "DELETE" })
|
||||
|
||||
Reference in New Issue
Block a user