fix: remove duplicate Zhipu usage provider

Keeps one Zhipu AI Coding Plan entry in usage settings
Preserves existing Zhipu aliases and config lookup
Removes duplicate backend quota registration
This commit is contained in:
Bohdan Triapitsyn
2026-05-19 14:49:03 +03:00
parent 0f015a495b
commit 3ac697adc7
6 changed files with 31 additions and 133 deletions
@@ -20,7 +20,6 @@ import * as zhipuaiCodingPlan from './zhipuai-coding-plan.js';
import * as minimaxCodingPlan from './minimax-coding-plan.js';
import * as minimaxCnCodingPlan from './minimax-cn-coding-plan.js';
import * as ollamaCloud from './ollama-cloud.js';
import * as zhipuai from './zhipuai.js';
const registry = {
claude: {
@@ -100,12 +99,6 @@ const registry = {
providerName: ollamaCloud.providerName,
isConfigured: ollamaCloud.isConfigured,
fetchQuota: ollamaCloud.fetchQuota
},
'zhipuai-coding-plan': {
providerId: zhipuai.providerId,
providerName: zhipuai.providerName,
isConfigured: zhipuai.isConfigured,
fetchQuota: zhipuai.fetchQuota
}
};
@@ -165,4 +158,4 @@ export const fetchNanoGptQuota = nanogpt.fetchQuota;
export const fetchMinimaxCodingPlanQuota = minimaxCodingPlan.fetchQuota;
export const fetchMinimaxCnCodingPlanQuota = minimaxCnCodingPlan.fetchQuota;
export const fetchOllamaCloudQuota = ollamaCloud.fetchQuota;
export const fetchZhipuaiQuota = zhipuai.fetchQuota;
export const fetchZhipuaiQuota = zhipuaiCodingPlan.fetchQuota;