Master's credential-lifecycle work taught the editor card that a pi-ai profile names `apiKeyEnv` only when a key is actually stored, so a route left blank keeps its provider-native auth path. The create card kept writing the derived reference unconditionally, so a route declared for a credential chain or ADC was born pointing at a reference nothing sets — and now rendered a red missing-key dot for it. Both cards apply one rule. The obsolete assertion moves with the behavior (the with-key case is covered by the neighbouring test), and the merged Models e2e golden shows the declared route unmarked rather than flagged.
32 lines
861 B
Markdown
32 lines
861 B
Markdown
- dialog "设置":
|
|
- navigation:
|
|
- text: 设置
|
|
- button "通用设置":
|
|
- img
|
|
- text: 通用设置
|
|
- button "模型":
|
|
- img
|
|
- text: 模型
|
|
- button "打开配置文件"
|
|
- button "关闭":
|
|
- img
|
|
- text: 关闭
|
|
- heading "模型" [level=2]
|
|
- paragraph: 填入各提供方的 API 密钥即可使用其模型。
|
|
- list:
|
|
- listitem:
|
|
- text: minimax-cn
|
|
- img "API 密钥已配置"
|
|
- button "编辑 minimax-cn": 编辑
|
|
- button "删除 minimax-cn": 删除
|
|
- listitem:
|
|
- text: Acme Gateway 自定义
|
|
- button "编辑 Acme Gateway (acme-gateway)": 编辑
|
|
- button "删除 Acme Gateway (acme-gateway)": 删除
|
|
- button "添加提供方":
|
|
- img
|
|
- text: 添加提供方
|
|
- button "添加自定义提供方":
|
|
- img
|
|
- text: 添加自定义提供方
|