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

Abierto
#40 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
csharp, unity
Área
game-dev, tooling

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

Lenguaje dominante
C#
Estrellas
4
Forks
0
Métricas de merge de PR
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de TMHSDigital/Unity-Developer-Tools

Todos los issues de TMHSDigital/Unity-Developer-Tools

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.