Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(ai-proxy): support custom displayProviderType for self-hosted provider #6493

Merged

Conversation

sfwn
Copy link
Member

@sfwn sfwn commented Feb 21, 2025

What this PR does / why we need it:

AI-Proxy support custom displayProviderType for self-hosted provider.

Which issue(s) this PR fixes:

ChangeLog

Language Changelog
🇺🇸 English AI-Proxy support custom displayProviderType for self-hosted provider
🇨🇳 中文 AI-Proxy 为自建供应商提供自定义类型用于展示

Copy link

codecov bot commented Feb 21, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 15.13%. Comparing base (cf722c4) to head (3331f57).
Report is 1 commits behind head on master.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #6493      +/-   ##
==========================================
- Coverage   15.13%   15.13%   -0.01%     
==========================================
  Files        3683     3683              
  Lines      377034   377034              
==========================================
- Hits        57059    57056       -3     
- Misses     314528   314530       +2     
- Partials     5447     5448       +1     
Flag Coverage Δ
by-github-actions 15.13% <ø> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

see 4 files with indirect coverage changes

@sfwn sfwn merged commit 1f08c37 into erda-project:master Feb 21, 2025
23 checks passed
@sfwn sfwn deleted the feat/ai-proxy-model-provider-display-type branch February 21, 2025 08:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging this pull request may close these issues.

2 participants