-
-
Notifications
You must be signed in to change notification settings - Fork 12.7k
修改模型展示名称后,对话页面模型选择框里联网和生图标识不能正常显示 #7160
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
Comments
Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible. |
The issue you're experiencing seems to be related to how the icons are determined in the model selection dropdown. The icons should be displayed based on the model's ID and its features, not the display name. The If the icons are not displaying correctly after changing the display name, it might be worth checking if the logic for determining the icons is inadvertently using the display name instead of the ID. Ensure that the To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other |
The issue you're experiencing with the icons not displaying correctly in the model selection dropdown after modifying the model's display name is likely due to how the codebase handles icon display logic. The If the icons are not displaying correctly, it might be worth checking if the To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other |
📦 部署环境
Docker
📦 部署模式
服务端模式(lobe-chat-database 镜像)
📌 软件版本
v1.75.2
💻 系统环境
Other Linux
🌐 浏览器
Chrome
🐛 问题描述
默认的Google预览版本模型的名称太长,于是我手动更新了一下展示名称;但是更新之后在对话页面模型选择框里联网和生图ICON标识不能正常显示了
但是功能是可以正常使用的,并且设置页里也可以正常显示联网和生图ICON标识
📷 复现步骤
手动修改模型的展示名称去掉Experimental字符串
🚦 期望结果
更新展示名称之后,在对话页面模型选择框里也能正常显示联网和生图ICON标识;应该根据id去判断icon的展示而不是使用展示名称去判断
📝 补充信息
No response
The text was updated successfully, but these errors were encountered: