Racket: Resyntax (the Racket static analyser/refactoring linter) runs in typed-racket and scribble CI; static-analysis SKIPs "not applicable to Racket"

Abierto
  • ¿Algo no está bien?
#278 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
Medio día
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Área
tooling

Línea de trabajo

Start from the corpus audit entries in corpus/ (the expected results and corpus/projects.toml pins for the typed-racket and scribble checkouts) and find where the static-analysis check returns SKIP with "not applicable to Racket". The issue also cites the Racket profile docs, which claim no common linter exists. Done means the check reports on Racket repos that run Resyntax and the docs no longer contradict it, which may need a maintainer decision on the expected behaviour first.

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

Descripción

Both repos run Resyntax on every pull request (and a scheduled autofixer); the Racket profile docs say "no linter the validator knows is in common use", but Resyntax is used by racket/racket, typed-racket, scribble and others.

Evidence from the corpus audit

racket/typed-racket, racket/scribble / static-analysis
  • kind: UNSUPPORTED
  • actual: SKIP: not applicable to Racket
  • expected: PASS: both repos run Resyntax, the Racket static analyser/refactoring linter, on every pull request (and a scheduled autofixer); the Racket profile docs say "no linter the validator knows is in common use", but Resyntax is used by racket/racket, typed-racket, scribble and rebellion's author (jackfirth/create-resyntax-pull-request).
  • evidence: racket__typed-racket/.github/workflows/resyntax-analyze.yml:49: run: xvfb-run racket -l- resyntax/cli analyze --local-git-repository . "origin/${GITHUB_BASE_REF}" --output-as-github-review --output-to-file ./resyntax-review.json; :38: packages: resyntax; racket__scribble/.github/workflows/resyntax-analyze.yml:49: same command; resyntax-autofixer.yml:33: uses: jackfirth/[email protected].
  • repro: a workflow step run: racket -l- resyntax/cli analyze --local-git-repository . origin/main.
  • confidence: medium

Found by the regression-corpus audit (235 real repositories, one or more per ecosystem profile; corpus and expected results in corpus/). Evidence is quoted from the audited checkouts at the commits pinned in corpus/projects.toml; <checkouts>/<owner>__<repo> is such a checkout.

🤖 Generated with Claude Code

https://claude.ai/code/session_01ByTXNqDWdM7HzezrFtEvQt

Lenguaje dominante
Python
Estrellas
4
Forks
1
Merge medio
10 h 41 min
PR fusionados (30 d)
79

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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 cpp-best-practices/project_validator

Todos los issues de cpp-best-practices/project_validator

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.