Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Epic: Cross-language capture architecture

Abierto
#278 1 comentario 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@vishnuv688 ya está trabajando en esto.

Desde el 12/8/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

capture-architecture

Stop paying for capture logic once per language. The Python adapter currently re-implements roughly 1,206 lines that are not language-specific (frames 193, screencast 213, snapshot 197, capturer 152, types 115, plus utils, sources, constants and log capture), against roughly 1,595 lines that genuinely are (instrumentation 386, bidi 412, lifecycle 363, transport 188, pytest plugin 124, backend resolution 122). A Java adapter would repeat the same split.

The damage so far has been behavioural rather than textual: force-anchor drain, recovery drain and document-start preload were all fixed in the JavaScript adapters and never propagated to Python. Shared code cannot prevent a fix from failing to propagate; a shared executable spec can.

Four levers under evaluation in #298: move post-processing behind the wire, push more work into the shared page script, generate contract types rather than mirroring them, and add a cross-adapter conformance suite. #299, #300 and #301 all wait on that decision.

#288 is the first consumer of whatever #298 decides, and now sits under #330 (trace mode for the Python adapter) rather than the adapter epic. Scoping #330 turned up a constraint #301 has to account for: trace mode deliberately runs no backend, so 'identical artifacts from the same stream' cannot mean routing every adapter through the live one. Recorded on #301.

Lenguaje dominante
TypeScript
Estrellas
10
Forks
2
Merge medio
1 d 2 h
PR fusionados (30 d)
24

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de webdriverio/devtools

Todos los issues de webdriverio/devtools

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.