Skip to content

feat(providers): 新增 API Route 内置润色渠道 - #1124

Closed
DennyHo0917 wants to merge 1 commit into
Open-Less:betafrom
DennyHo0917:feat/api-route-polish-provider
Closed

DennyHo0917 wants to merge 1 commit into
Open-Less:betafrom
DennyHo0917:feat/api-route-polish-provider

Conversation

@DennyHo0917

Copy link
Copy Markdown

摘要

没有关联 issue。

新增 API Route 作为内置文字润色渠道,沿用现有 OpenAI 兼容请求和模型拉取流程。渠道为可选项,不改变默认渠道或自动选择逻辑。

修复 / 新增 / 改进

  • 在 Rust Core 注册 api-route,默认接口为 https://global.api-route.com/v1,默认模型为 deepseek-v4-flash,并接入现有密钥、验证和润色流程。
  • 在设置页、概览页及所有现有前端语言中显示 API Route;同步更新 Linux egui 标签、浏览器预览目录和中英文 README。
  • 增加 Core 描述符与实际润色请求测试。

兼容

  • 不包含:ASR 接入、默认渠道变更、专用请求协议或自动选用 API Route。
  • 对现有用户 / 本地环境 / 构建流程的影响:无;仅增加一个可手动配置的渠道。

测试计划

  • cargo test --locked -p openless-core:1045 通过、1 忽略。
  • npm run build;npx tsx src/lib/ipc/providers.test.ts;npx tsx src/pages/settings/ProvidersSection.test.ts。
  • Windows 本地 Vite 预览手动检查:设置 → AI 服务与模型 → 添加渠道,可选择 API Route,并显示预设接口与模型。
  • rustfmt --check 与 git diff --check。
  • 真实 API Route 请求:本地未提供 API key,未消耗线上额度;Windows 原生安装包未运行。

npm test 的前置构建通过,但完整前端测试在未修改的 scripts/ci-cache-usage.test.mjs 上失败:该脚本在 Windows 上读取临时 deleted.tsv 时收到 ENOENT。相关 Provider 前端测试已单独通过。

appergb added a commit that referenced this pull request Sep 30, 2026
Integrate ASR/Omni fixes, API Route, Android IME and confirmation-based vocabulary learning. Complete settings transitions and macOS single-item credential storage. Synchronize all application versions to 2.0.0-Beta.4+build.20260930.

Integrated PRs: #1116, #1120, #1121, #1123, #1124, #1067 and #1128. Linux #1117 remains independent and is excluded from automatic release.

Validated: full cross-platform CI, 18 UI motion cases, 112 frontend test files, 1245 Core tests (1 ignored) and 572 macOS native tests.

Co-authored-by: HKLHaoBin <we3q@qq.com>
@appergb appergb closed this Sep 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants