PHP (Composer + PHPUnit/Pest) support: tracking issue

Aberta
#88 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
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
30/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
php, typescript
Domínio
devtools, testing-qa

Direção de pesquisa

This is a tracking issue, so pick one unchecked step and read docs/adding-an-adapter.md and src/repo/adapters/python.ts first, since the issue names the Python adapter as the closest model. Adapter registration lives in src/repo/adapters/index.ts, and the release boundary is in docs/release-boundary.md. Done means one PR for that step, with the uncertain cases recording a blockers entry rather than returning an empty graph. Ask in the thread before starting, because the design questions are open.

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

Descrição

adapter enhancement help wanted

DiffCI works out what a change needs from CI, starting with the tests it affects, so AI coding agents (and people) can run them before pushing. It supports JS/TS, Vue, Go, Maven and pytest today. PHP is open for contributors and design partners.

First supported setup: a Composer project tested with PHPUnit or Pest, selecting at the test-file level.

Steps (each is one PR; take any that are unblocked):

  • Map classes to files through Composer's PSR-4 autoload and autoload-dev
  • Build the file graph from use statements, new, static calls and extends/implements
  • Discover tests from phpunit.xml (or phpunit.xml.dist) test suites and Pest's tests/
  • Generate phpunit / pest commands for the selected test files
  • Fall back with a reason on what the graph can't see: string class names, $container->get(...), framework service wiring (Laravel, Symfony), composer.json / composer.lock changes
  • Register the adapter in REPOSITORY_ADAPTERS (src/repo/adapters/index.ts) and add it to the release boundary
  • Replay on one public PHP repository and publish the report

Ground rules

  • When the adapter is unsure, it records a blockers entry and DiffCI runs the full suite. An empty graph must never look like "nothing affected".
  • Read the adapter guide first; the Python adapter (src/repo/adapters/python.ts) is the closest model.
  • Discuss design questions here, so every step stays consistent.

Using PHP (plain, Laravel or Symfony) and want to help, or have a repository we could test against? Say so below. 👍 this issue if you'd use it; reactions on the language tracking issues decide what comes after.

Linguagem predominante
TypeScript
Estrelas
0
Forks
4
Merge médio
18h 41min
PRs com merge (30d)
48

Preparar o ambiente

Abrir no Codespaces

Inicia o contêiner de desenvolvimento do projeto no navegador, com a sua própria conta do GitHub.

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 DiffCI/core

Todas as issues de DiffCI/core

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

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