pjandro/OmniRoute
1
0
Fork 0
mirror of https://github.com/diegosouzapw/OmniRoute.git synced 2026-09-18 21:02:50 +03:00
Code Issues Packages Projects Releases Wiki Activity

test: expect the jina alias prefix in the custom-model catalog case

Browse Source 
The custom-model assertions expected ids prefixed `jina-ai/`, but the catalog
prefixes model ids with the provider alias, which is `jina`. The synced-model
test directly above asserts `jina/` and passes, so the two cases contradicted
each other within the same file.

The expectation predates the alias: the test was written in v3.7.9 (2026-05-04)
and `alias: "jina"` was added in v3.8.36 (2026-06-25).

Aligns the two assertions with the sibling test and with the product. The file
now passes 44/44 (was 43 with 1 failure).

Confirmed the assertions still bite: renaming the alias to `jina-XX` fails
exactly these two cases.
This commit is contained in:
anhtahaylove
2026-09-11 12:29:40 +07:00
parent 152d95108c
commit 8d371d4e86
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
tests/unit/models-catalog-route.test.ts
View File

@@ -1092,9 +1092,9 @@ test("v1 models catalog does not duplicate custom Jina specialty models", async
assert.equal(response.status, 200);
assert.equal(visibleJinaEmbeddingRows.length, 1);
assert.equal(visibleJinaEmbeddingRows[0].id, "jina-ai/jina-embeddings-v5-text-small");
assert.equal(visibleJinaEmbeddingRows[0].id, "jina/jina-embeddings-v5-text-small");
assert.equal(visibleJinaRerankRows.length, 1);
assert.equal(visibleJinaRerankRows[0].id, "jina-ai/jina-reranker-v3");
assert.equal(visibleJinaRerankRows[0].id, "jina/jina-reranker-v3");
});
test("v1 models catalog exposes image model input and output modalities for advanced image providers", async () => {