MCP baseline filtering untested for validate_* tools and report categories

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

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
77/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
typescript
Área
devtools, testing

Línea de trabajo

Start with the baseline filtering in src/tools/scenes.ts and the existing tests in test/tools.test.ts:194-213. Add the listed cases for scene, project config, registry, and report category filtering, path resolution, invalid JSON, and consecutive lint calls. Run npm run build && npm test; done when the new tests pass and the report category counts equal totalFindings.

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

Descripción

good first issue severity: low testing

Summary

MCP baseline support is tested only for lint_project and the lint category of project_report. The per-category filtering for scenes, project and registries is never exercised.

Where

  • src/tools/scenes.ts:26-30, src/tools/scenes.ts:62-65, src/tools/scenes.ts:79-85, src/tools/scenes.ts:102-119
  • test/tools.test.ts:194-213

Test cases to add

  • validate_scenes with a valid baseline plus a new broken .tscn: only the new file is returned, and baselined and count are correct.
  • validate_project_config with a baseline: an old bad autoload is absorbed and a new one is reported.
  • validate_registries with a baseline: entries is preserved, and only new dangling paths are returned.
  • project_report with a baseline on a copy of test/fixtures/scene-project: each category is filtered independently, and errorCount + warningCount + infoCount === totalFindings.
  • An absolute baseline path works, and a relative one resolves against the project root.
  • Invalid baseline JSON returns isError.
  • Editing a file between two consecutive lint_project calls is reflected in the second call. This guards the per-run read cache in src/project/files.ts.

Getting started

  • Relevant files: src/tools/scenes.ts, test/tools.test.ts
  • How to run tests: npm run build && npm test

Filed by repo-audit/full-audit at e836036. Severity: low. Effort: S. audit-key: testing|src/tools/scenes.ts|baseline

Lenguaje dominante
TypeScript
Estrellas
0
Forks
6
Merge medio
1 d 21 h
PR fusionados (30 d)
8

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/godot-correctness-mcp

Todos los issues de TMHSDigital/godot-correctness-mcp

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.