Feature: generate a version-accurate Unity API index for lookup_api

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

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
35/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
csharp, unity
領域
game-dev, tooling

研究方向

Start by reading the existing lookup_api implementation and the lifecycle-only weekly data workflow; the issue does not name their file paths. Then assess Unity ScriptReference or reference assemblies as data sources and how analyze_project determines the Unity version. Done means version-selectable generated indexes provide accurate signatures and obsolete warnings for supported public UnityEngine types while keeping the data size reasonable.

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

描述

feature mcp-server priority: medium

Why it matters

A hand-curated list of 59 entries cannot compete with the model's own memory, so lookup_api adds little value today. What models genuinely lack is version-accurate facts: which members exist in Unity 6.x, which are obsolete, and what the exact signatures are. A generated index makes the tool authoritative instead of decorative, and fulfils the M2 roadmap goal of "500+ entries".

Proposal

  • A build script that generates unity_api_index.json from Unity's ScriptReference (or from the UnityEngine/UnityEditor reference assemblies via reflection / System.Reflection.Metadata), capturing type, member, signature, [Obsolete] message, and since-version.
  • Store per Unity version (6000.0 LTS, latest 6.x), selectable via a unity_version argument (defaulting to the version found by analyze_project).
  • Keep the curated entries as "examples/notes" layered on top.
  • Ranked fuzzy search; return obsolete status and replacement prominently.
  • Run the generator in the weekly data workflow (as a PR), replacing the current lifecycle-only refresh.

Done when

lookup_api returns accurate signatures and obsolete warnings for any public UnityEngine type in the supported versions, with size kept reasonable (compressed or SQLite).

主要語言
C#
星號
4
分支
0
PR 合併指標
30 天內沒有已合併 PR

環境準備

從這裡開始

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

TMHSDigital/Unity-Developer-Tools 的其他 Issue

查看 TMHSDigital/Unity-Developer-Tools 的全部 Issue

相似的 Issue

更多 C# Issue

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

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