Django support: design partners and contributors wanted

Aperta
#87 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
42/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
django, python
Ambito
ci-cd, testing

Direzione di ricerca

Read docs/adding-an-adapter.md, then the Python adapter in src/repo/adapters/python.ts, which this work extends. Pick one unblocked step, such as detecting a Django project from manage.py or DJANGO_SETTINGS_MODULE, and confirm the design with the thread first. Done means the adapter recognises the project and a fixture repo gets Django-aware selection or a blockers fallback instead of an empty graph.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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. Python projects tested with pytest are supported today (#61, #75). Django is next, and this is open for contributors and design partners.

Why Django needs its own work: much of a Django project is wired by strings, not imports, so a plain import graph misses it:

  • INSTALLED_APPS, MIDDLEWARE, ROOT_URLCONF, AUTH_USER_MODEL and include("app.urls") name modules as dotted strings
  • templates, static files and fixtures are found by app directory, not imported
  • a settings.py change can affect everything, or nothing
  • many projects run manage.py test (unittest discovery), not pytest

Today these show up as missed edges or a full-suite fallback.

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

  • Detect a Django project (manage.py, DJANGO_SETTINGS_MODULE, pytest-django settings)
  • Treat dotted-string settings and include() targets as imports
  • Map templates, static files and fixtures to the app that owns them
  • Narrow settings.py changes where the changed setting is known, else fall back with a reason
  • Generate manage.py test <labels> commands when the project doesn't use pytest
  • Replay on one public Django 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 where this builds.
  • Discuss design questions here, so every step stays consistent.

Run a Django codebase? Try npx --yes @diffci.com/diffci@latest check --base origin/main --head HEAD and post what it selected or the fallback reason below. That tells us which step to do first. 👍 this issue if you'd use it.

Lingua principale
TypeScript
Stelle
0
Fork
4
Merge medio
18h 41m
PR unite (30g)
48

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di DiffCI/core

Tutte le issue di DiffCI/core

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.