Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Generate the adapter capability matrix instead of maintaining three by hand

Aberta
  • Algo errado?
#402 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
42/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
typescript
Domínio
build-system, documentation, tooling

Direção de pesquisa

Read the Capability table in README.md, CrossFrameworkSupport.md, MobileTesting.md, and CLAUDE.md’s Known debt to inventory the current rows, adapters, and reasons before locating the repository’s generation or build entry point. Done means one declared source generates all three tables, requires reasons for exemptions, rejects undeclared adapters, and visibly distinguishes proven from declared cells.

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

Descrição

capture-architecture enhancement

Part of #278

Three capability matrices are maintained by hand today: the Capability table in
this repo's README.md, CrossFrameworkSupport.md on the docs site, and the
adapter table on MobileTesting.md. The first two carry three adapter columns.
The mobile one carries four.

The Python adapter published to PyPI on 2026-09-29 and has yet to appear in the
other two, which is the whole problem in one observation: a markdown table has no
way to notice that a fourth adapter now exists. It is the epic's complaint about
capture logic, in prose rather than code.

The tables are otherwise good. They already do the thing worth keeping, which is
naming the capability, marking it per adapter, and footnoting why an adapter
falls short rather than leaving a bare gap. That part should survive.

What to change

Make the matrix an output rather than a document. One declared source listing
every capability and, per adapter, either support or an exemption carrying a
required reason. Render it to the README and to the docs pages.

That buys three things a table cannot:

  • Adding an adapter turns every unlisted capability into an error, rather than
    into a column nobody updated.
  • A reason becomes mandatory. Today a warning marker with no footnote is valid
    markdown; in a declared source, an exemption without a reason does not build.
    Most of the reasons already exist in CLAUDE.md's Known debt in more detail
    than the current footnotes carry, so this is largely relocation.
  • The README and both docs tables render from one source and cannot disagree.
Relationship to #300

Complementary, and deliberately separable. Where a capability is testable over
the emitted frame stream, its cell can be proven by the conformance suite
rather than declared. Where it is not testable from a stream (inline Allure
attach, Cucumber nesting, live-dashboard overlay), the cell stays a declared
claim.

The two states must be visibly distinct in the rendered table. Most cells will
start declared, and a matrix that reads as conformance-backed when only a few
rows are is worse than an honest hand-maintained one.

This issue is useful whether or not #300 is built, which is why it is not folded
into it.

Acceptance criteria

One declared source of capabilities and per-adapter support. An exemption
requires a reason. The README table and the docs tables are generated from it,
with no adapter column missing. Adding an adapter without declaring its support
fails the build. Proven and declared cells are distinguishable in the output.

Size: M.

Linguagem predominante
TypeScript
Estrelas
10
Forks
2
Merge médio
13h 52min
PRs com merge (30d)
24

Preparar o ambiente

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 webdriverio/devtools

Todas as issues de webdriverio/devtools

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.