mirror of
https://github.com/diegosouzapw/OmniRoute.git
synced 2026-09-13 18:32:12 +03:00
65e81158ab
Landed with the design call resolved per the owner's pick — **option 1**: the synced store is now endpoint-agnostic (persistDiscoveredModels and managedModelImport no longer drop non-chat models at write time), and chat selectability moved to read time (auto-pool expansion in autoStrategy applies filterChatSelectableModels; the models-route projection already had its chatOnly filter). Your discovery test now passes end-to-end (3/3): /api/show capabilities persist per connection and image/embedding requests route through the advertising host. Reconciliation notes: conflicted areas merged onto the current tip (adobe discovery import, requestedModel preflight signature, resolvedProvider fast-path coexists with the synced-route override — explicit resolution wins); carried base-red drains (#10055 memoization, #11071 test variants) dropped as already-landed; the managed-model-import exclusion test was propagated to the new contract (image/video models persist; the read filter still hides them from chat pickers — pinned by a new assertion). Full battery: 205/206 focused (the one red is a confirmed periodic-timer timing flake on the loaded devbox — 20/20 isolated), autoCombo vitest 30/30, combo suites 46/46, gates + typecheck clean. Thank you @yourspraveen — the capability probe + routing design was right; it just needed the store contract opened up. Fixes #11087.
38 lines
1.7 KiB
TypeScript
38 lines
1.7 KiB
TypeScript
import test from "node:test";
|
|
import assert from "node:assert/strict";
|
|
|
|
// Issue #10096: Kimi Code API key validates OK but Save returns 400 "Invalid provider".
|
|
//
|
|
// Root cause: the unified Kimi Code dashboard card's API-key branch posted
|
|
// provider: "kimi-coding" (an OAuth-primary managed id, NOT an admitted
|
|
// API-key connection id) to POST /api/providers, which the backend rejects.
|
|
// The dedicated managed API-key id "kimi-coding-apikey" IS admitted.
|
|
//
|
|
// Fix: resolveApiKeySaveProviderId() in useApiKeySave.ts remaps the posted
|
|
// provider id to "kimi-coding-apikey" for the API-key save flow only, while
|
|
// the OAuth flow (which never calls this hook) keeps posting "kimi-coding".
|
|
|
|
const { isManagedProviderConnectionId } = await import("../../src/lib/providers/catalog.ts");
|
|
const { resolveApiKeySaveProviderId } = await import(
|
|
"../../src/app/(dashboard)/dashboard/providers/[id]/hooks/useApiKeySave.ts"
|
|
);
|
|
|
|
test("Kimi Code API-key save flow remaps to the admitted managed API-key id", () => {
|
|
assert.equal(
|
|
resolveApiKeySaveProviderId("kimi-coding"),
|
|
"kimi-coding-apikey",
|
|
"the unified Kimi Code card's API-key save flow must post kimi-coding-apikey, not kimi-coding"
|
|
);
|
|
assert.equal(
|
|
isManagedProviderConnectionId(resolveApiKeySaveProviderId("kimi-coding")),
|
|
true,
|
|
"the remapped id must be an admitted managed provider connection id (POST /api/providers accepts it)"
|
|
);
|
|
});
|
|
|
|
test("resolveApiKeySaveProviderId leaves every other provider id untouched", () => {
|
|
assert.equal(resolveApiKeySaveProviderId("openai"), "openai");
|
|
assert.equal(resolveApiKeySaveProviderId("kimi-coding-apikey"), "kimi-coding-apikey");
|
|
assert.equal(resolveApiKeySaveProviderId("qoder"), "qoder");
|
|
});
|