Probe the chat endpoint for providers with no schemaEndpointId (dashscope-cn, lovable, nvidia, vertex-anthropic, kimi)

未关闭
#716 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
38/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
typescript
领域
backend, data

调研方向

Start in src/server/providers/probes/ and read the existing opencode-go probe as the template for binding an endpoint only to the exact model and route. Then inspect the gap report rows for dashscope-cn, lovable, nvidia, google-vertex-anthropic, and kimi to see which provider keys are available and which routes have documented endpoints. Add one probe per provider where a key exists, set verifiedAt so rows are served as probe-verified, and confirm the endpoint count rises; note any provider that should use a docs parser instead in the PR.

由索引模型根据 Issue 内容生成。

描述

Problem

schemaEndpointId is null on about 220 chat rows: dashscope-cn 129, lovable 26, nvidia 20, google-vertex-anthropic 14, kimi-code-plan-cn 6, kimi-code-plan-global 6 (gap report, 2026-11-21). The probe framework already records this fact (src/server/providers/probes/), but only opencode-go has a probe file.

Ask

  • Add a probe file for each provider above, where we hold its key.
  • Bind the endpoint only for the exact model and route a record names, as opencode-go does.
  • A provider whose docs state the route should get a docs parser instead; say which in the PR.

Acceptance

  • endpoint in the gap report rises for each provider probed.
  • Each record has verifiedAt and is served as probe-verified.
主要语言
TypeScript
星标
0
派生
1
平均合并
5 小时 40 分钟
30 天内合并 PR
193

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

TanStack/schemas 的其他 Issue

查看 TanStack/schemas 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。