Docs: roadmap lists Rust as not yet supported, but the Rust (Cargo) adapter ships experimentally

未關閉
#290 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

@FredApps 已經在處理了。

開始於 2026年11月17日。

  • #291 來自 @FredApps —— 未關閉

評估

難度
1/5
預估耗時
1-3 小時
新手友好度
35/100
Issue 類型
文件
描述清晰度
描述清楚
活躍度
停滯
技術堆疊
typescript
領域
documentation

研究方向

Read docs/roadmap.md and compare its “Language support” section with the Rust wording in README.md, docs/release-boundary.md, and docs/using-diffci.md. Update the roadmap to describe Rust (Cargo) as experimentally supported with the README caveat, and list Django, PHP, and Gradle as next while keeping tracking issue #62. Done when the roadmap matches those details.

由索引模型根據 Issue 內容生成。

描述

docs/roadmap.md ("Language support") says:

JS/TS, Vue, Go, Maven and Python (pytest) are supported today. Django, Rust, PHP and Gradle are next and open for contributors

Rust is no longer only "next". On main @ 40aa308:

  • src/repo/adapters/index.ts registers rustAdapter in REPOSITORY_ADAPTERS, next to Vue, Go, Maven and Python.
  • README.md lists "experimentally, Cargo workspaces (Rust support is new and has not yet narrowed a real project's history, so expect full runs there for now)". Its Contributing section names only Django and PHP as next.
  • docs/release-boundary.md lists "experimentally, Cargo workspace (crate-level Rust) analysis".
  • docs/using-diffci.md has a "Rust adapter safety" section.

So the roadmap tells a reader that Rust isn't supported at all, while the engine and the other docs say it is, experimentally.

Expected: the roadmap says Rust (Cargo) is supported experimentally, with the same caveat as the README, and lists only Django, PHP and Gradle as next. The Rust tracking issue (#62) stays in the list, because it still tracks open steps.

Docs-only.

主要語言
TypeScript
星號
0
分支
4
平均合併
18 小時 41 分鐘
30 天內合併 PR
48

環境準備

在 Codespaces 中開啟

在瀏覽器裡用你自己的 GitHub 帳號啟動這個專案的開發容器。

  • 沒有 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

DiffCI/core 的其他 Issue

查看 DiffCI/core 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。