mirror of
https://github.com/diegosouzapw/OmniRoute.git
synced 2026-09-19 21:32:20 +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.
44 lines
1.9 KiB
TypeScript
44 lines
1.9 KiB
TypeScript
import { test } from "node:test";
|
|
import assert from "node:assert/strict";
|
|
|
|
import { isRoutableProviderPrefix } from "../../src/lib/ccDiscoveryAliasResolve.ts";
|
|
|
|
/**
|
|
* Regression guard for the "listed but rejected" cc-discovery alias mismatch.
|
|
*
|
|
* The /v1/models catalog mirrors `claude/<provider>/<model>` ids based purely on
|
|
* the alias gate (src/app/api/v1/models/ccAliasPredicate.ts — it does NOT consult
|
|
* any provider registry). The request path additionally required the prefix to be
|
|
* an `open-sse` REGISTRY entry or an operator-defined custom node.
|
|
*
|
|
* Enterprise-cloud providers such as `azure-ai` / `azure-openai` live in the
|
|
* provider CATALOG (src/shared/constants/providers/apikey/enterprise-cloud.ts)
|
|
* and route fine directly (`azure-ai/Phi-4` → 200), but have no `open-sse`
|
|
* registry entry. So the catalog advertised `claude/azure-ai/<model>` while the
|
|
* request path refused to strip it — the id fell through with `claude` parsed as
|
|
* the provider, and every request was routed to the Claude provider instead.
|
|
*
|
|
* These assertions pin the predicate to "can the router actually reach it",
|
|
* which is the property the catalog side already assumes.
|
|
*/
|
|
|
|
test("catalog-only enterprise-cloud providers are routable (azure-ai regression)", () => {
|
|
assert.equal(isRoutableProviderPrefix("azure-ai"), true);
|
|
assert.equal(isRoutableProviderPrefix("azure-openai"), true);
|
|
});
|
|
|
|
test("open-sse registry providers stay routable", () => {
|
|
assert.equal(isRoutableProviderPrefix("openai"), true);
|
|
assert.equal(isRoutableProviderPrefix("anthropic"), true);
|
|
});
|
|
|
|
test("provider aliases resolve too", () => {
|
|
// `azure` is the declared alias of the `azure-openai` catalog entry.
|
|
assert.equal(isRoutableProviderPrefix("azure"), true);
|
|
});
|
|
|
|
test("an unknown prefix is not routable", () => {
|
|
assert.equal(isRoutableProviderPrefix("definitely-not-a-provider-xyz"), false);
|
|
assert.equal(isRoutableProviderPrefix(""), false);
|
|
});
|