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

Aberta
  • Algo errado?
#278 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
3/5
Tempo estimado
Meio dia
Facilidade para iniciantes
35/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Domínio
tooling

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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

Linguagem predominante
Python
Estrelas
4
Forks
1
Merge médio
10h 41min
PRs com merge (30d)
79

Preparar o ambiente

Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de cpp-best-practices/project_validator

Todas as issues de cpp-best-practices/project_validator

Issues semelhantes

Mais issues de Python

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.