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

Offen
#40 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
35/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
csharp, unity
Bereich
game-dev, tooling

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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).

Vorherrschende Sprache
C#
Sterne
4
Forks
0
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus TMHSDigital/Unity-Developer-Tools

Alle Issues in TMHSDigital/Unity-Developer-Tools

Ähnliche Issues

Weitere Issues zu C#

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.