fix(test): repair the v2/main typecheck break from a semantic conflict

#2094 retyped `RequestMetadata` as `Record<string, StrictJsonValue>` and
#2087, merged minutes later, added a `updateServerSettings` case passing
`metadata: []`. Neither touched the other's lines, so both merged clean
and `tsc -b` has failed on v2/main ever since (TS2322: 'never[]' is not
assignable to 'RequestMetadata').

One occurrence repo-wide; `[]` → `{}`. Carried here rather than on its
own branch because this PR merged v2/main and inherited the break, so its
CI cannot pass without it.

Signed-off-by: cliffhall <cliff@futurescale.com>
This commit is contained in:
cliffhall 2026-08-23 23:10:12 -04:00
commit ab92bab5aa

View file

@ -1307,7 +1307,7 @@ describe("useServers", () => {
result.current.updateServerSettings(existing, {
headers: [],
env: [],
metadata: [],
metadata: {},
roots: [],
connectionTimeout: 5000,
requestTimeout: 30000,