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

Ouverte
#88 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
30/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
php, typescript
Domaine
devtools, testing-qa

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
TypeScript
Étoiles
0
Forks
4
Merge moyen
18 h 41 min
PR mergées (30 j)
48

Préparer son environnement

Ouvrir dans Codespaces

Lance le conteneur de développement du projet dans votre navigateur, avec votre propre compte GitHub.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de DiffCI/core

Toutes les issues de DiffCI/core

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.