feat: differentiate fetch models error messages by failure type

Distinguish between missing API key, missing endpoint, auth failure,
unsupported provider (404/405), and timeout errors instead of showing
a generic failure toast for all cases.
This commit is contained in:
Jason
2026-04-03 23:40:49 +08:00
parent f200feebe4
commit 84998aa217
9 changed files with 119 additions and 18 deletions
@@ -33,7 +33,11 @@ import {
copilotGetModelsForAccount,
} from "@/lib/api/copilot";
import type { CopilotModel } from "@/lib/api/copilot";
import { fetchModelsForConfig, type FetchedModel } from "@/lib/api/model-fetch";
import {
fetchModelsForConfig,
showFetchModelsError,
type FetchedModel,
} from "@/lib/api/model-fetch";
import type {
ProviderCategory,
ClaudeApiFormat,
@@ -186,7 +190,10 @@ export function ClaudeFormFields({
const handleFetchModels = useCallback(() => {
if (!baseUrl || !apiKey) {
toast.error(t("providerForm.fetchModelsFailed"));
showFetchModelsError(null, t, {
hasApiKey: !!apiKey,
hasBaseUrl: !!baseUrl,
});
return;
}
setIsFetchingModels(true);
@@ -203,7 +210,7 @@ export function ClaudeFormFields({
})
.catch((err) => {
console.warn("[ModelFetch] Failed:", err);
toast.error(t("providerForm.fetchModelsFailed"));
showFetchModelsError(err, t);
})
.finally(() => setIsFetchingModels(false));
}, [baseUrl, apiKey, isFullUrl, t]);