Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

API improvements roadmap

Aperta
  • Qualcosa non va?
#1,581 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à
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
15/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
docker, node.js, typescript
Ambito
api, backend

Direzione di ricerca

Start with the roadmap tracks and dependency graph in this issue to understand how the API review is divided; the linked issues contain the individual changes and their files, tests, and acceptance criteria. This tracking issue is complete when the listed API review work is resolved and the roadmap is up to date.

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

Descrizione

maintenance

Tracking issue for an API review of testcontainers 12.2.0 and its modules: correctness bugs in the public API, gaps against the Java, Go and .NET implementations, and changes that would make the library nicer to use.

The issues are grouped into tracks that can be worked on in parallel. Each issue ends with a Dependencies section that uses three terms:

  • Blocked by: cannot usefully start before the other issue lands.
  • Stack on: changes the same code. Open it as a stacked pull request on top of the other one (gh stack).
  • Coordinate with: overlapping lines or a shared decision. Whoever lands second rebases.

Stacks

Chains where the order matters. Everything else is independent.

  • withEnvironment: #1519 → #1543
  • start() and builder state: #1520 first, then in parallel #1550, #1556, #1557, and #1554 → #1555
  • Reuse: #1522 → #1552 → #1553, and #1522 → #1547
  • exec: #1525 and #1531 → #1548
  • Compose flags: #1524 → #1530
  • Wait strategies: #1523, #1533 and #1534 first, then #1558 → #1559 and #1560, then #1582
  • Networks: #1535 → #1561, and #1536 → #1567
  • Configuration and diagnostics: #1569 → #1570, and #1571 → #1572
  • Entry point: #1558 and #1561 → #1562; #1528 → #1580
  • Module shape: #1520 and #1554 → #1563, after the started-container additions

Next major

Labelled major: #1521, #1558, #1561, #1562, #1563, #1582.

Labelled patch or minor but with a behaviour change to decide on: #1523, #1527, #1529, #1557, #1577.

Tracks

Foundations
  • #1518 (can start now)
  • #1580
  • #1579 (can start now)
  • #1577 (can start now)
  • #1576 (can start now)
Builder state and start()
  • #1519 (can start now)
  • #1543
  • #1520 (can start now)
  • #1550
  • #1556
  • #1557
  • #1554
  • #1555
  • #1527 (can start now)
  • #1530
  • #1529 (can start now)
  • #1531 (can start now)
Reuse
  • #1521 (can start now)
  • #1522 (can start now)
  • #1552
  • #1553
Wait strategies
  • #1523 (can start now)
  • #1533 (can start now)
  • #1534 (can start now)
  • #1558 (can start now)
  • #1559
  • #1560
  • #1582
Started containers
  • #1525 (can start now)
  • #1548
  • #1544 (can start now)
  • #1545 (can start now)
  • #1546 (can start now)
  • #1547
  • #1549 (can start now)
  • #1541 (can start now)
  • #1583 (can start now)
Errors, logging and diagnostics
  • #1532 (can start now)
  • #1571 (can start now)
  • #1572
  • #1568 (can start now)
  • #1569 (can start now)
  • #1570
Networks, volumes and groups
  • #1535 (can start now)
  • #1536 (can start now)
  • #1567
  • #1564 (can start now)
  • #1565 (can start now)
Images and Compose
  • #1537 (can start now)
  • #1551 (can start now)
  • #1524 (can start now)
  • #1540 (can start now)
  • #1573 (can start now)
Public surface (next major)
  • #1528 (can start now)
  • #1561
  • #1562
  • #1563
Modules
  • #1526 (can start now)
  • #1538 (can start now)
  • #1539 (can start now)
  • #1574 (can start now)
  • #1575 (can start now)
Docs and tooling
  • #1542 (can start now)
  • #1578 (can start now)

Dependency graph

Hard dependencies only (blocked by, stack on).

graph LR
  n63["#1582"]
  n62["#1567"]
  n56["#1580"]
  n52["#1557"]
  n51["#1554"]
  n50["#1556"]
  n49["#1552"]
  n48["#1553"]
  n47["#1570"]
  n46["#1569"]
  n45["#1555"]
  n44["#1572"]
  n43["#1571"]
  n38["#1560"]
  n37["#1543"]
  n35["#1536"]
  n33["#1550"]
  n32["#1548"]
  n31["#1547"]
  n27["#1563"]
  n26["#1559"]
  n25["#1558"]
  n22["#1535"]
  n14["#1530"]
  n12["#1531"]
  n11["#1561"]
  n10["#1562"]
  n08["#1528"]
  n07["#1525"]
  n06["#1524"]
  n05["#1520"]
  n04["#1519"]
  n02["#1522"]
  n06 --> n14
  n04 --> n37
  n02 --> n31
  n07 --> n32
  n12 --> n32
  n05 --> n33
  n02 --> n49
  n02 --> n48
  n49 --> n48
  n05 --> n51
  n51 --> n45
  n05 --> n50
  n05 --> n52
  n25 --> n26
  n25 --> n38
  n22 --> n11
  n25 --> n10
  n11 --> n10
  n05 --> n27
  n51 --> n27
  n35 --> n62
  n46 --> n47
  n43 --> n44
  n08 --> n56
  n25 --> n63
  n38 --> n63

43 of 64 issues have no hard dependency.

Lingua principale
TypeScript
Stelle
2.6k
Fork
274
Merge medio
1g 14h
PR unite (30g)
44

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 testcontainers/testcontainers-node

Tutte le issue di testcontainers/testcontainers-node

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.