Feature: check_code tool to flag deprecated and anti-pattern Unity APIs with line numbers

Abierto
#39 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 locating deprecated_patterns.json, the existing lookup_api MCP tool, and the performance-optimization and csharp rules mentioned in the issue. Define the scanner and data schema around those entry points, then add a fixture covering each listed pattern and verify the reported line numbers, replacements, and reasons. Done means check_code flags every fixture pattern with the correct line number.

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

Descripción

feature mcp-server priority: medium

Why it matters

deprecated_patterns.json already maps legacy APIs to replacements, but it is only used as a side-warning in lookup_api. Developers upgrading to Unity 6 (or AI agents reviewing code) want "scan this file and tell me what to change". That is concrete, high-value, and easy to demo.

Proposal

New MCP tool check_code(code | file_path):

  • Regex/token match against deprecated_patterns.json plus new Unity 6 renames (velocity -> linearVelocity, drag -> linearDamping, FindObjectsOfType -> FindObjectsByType, CGPROGRAM in URP, Camera.main in Update, GetComponent in Update, GameObject.Find in hot paths, async void outside event handlers, new WaitForSeconds in loops).
  • Returns line numbers, the replacement, and a reason, optionally with a suggested patch.
  • Extend the data schema with pattern (regex), severity, autofix.

Stretch: ship the same patterns as a Roslyn analyzer package for Unity, so the checks run in the editor and CI too.

Done when

check_code flags every pattern in a fixture file with correct line numbers, and the performance-optimization and csharp rules point the agent at it.

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.