Replace the hand-written opencode-go route records with an observed or docs-read source

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
25/100
Issue 类型
重构
描述清晰度
基本清楚
活跃度
活跃
技术栈
typescript
领域
api, backend

调研方向

Start in src/server/providers/probes/ and read the legacy opencode-go records alongside what #742 changed, then check how other providers' probes prove a route so you can tell an observed record from a typed one. OpenCode's go.mdx gives only the base path, so either add OPENCODE_GO_API_KEY as a Worker secret and write a route-proving probe, or find an OpenCode page listing :generateContent and :streamGenerateContent. Done means no typed records remain under src/server/providers/probes/ and /v1/status no longer reports them as stale.

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

描述

Problem

After #742 the only hand-written probe records left are the legacy opencode-go ones under src/server/providers/probes/. They bind the :generateContent and :streamGenerateContent routes on opencode-go/gemini-4-argon-contributor and set that row's trainsOnRequestData. Nothing re-dates them, so /v1/status counts them as stale probes from 2027-01-22. OpenCode's go.mdx states only the base path, and the Worker holds no OpenCode Go key.

Ask

Observe the routes from the Worker (needs OPENCODE_GO_API_KEY as a Worker secret and a probe that can prove a route), or find an OpenCode page that states them, then delete the records.

Acceptance

  • No file under src/server/providers/probes/ holds a typed record.
主要语言
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 摘要。