Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Generate the adapter capability matrix instead of maintaining three by hand

オープン
  • 何か問題がありますか？
#402 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
42/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
typescript
領域
build-system, documentation, tooling

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.

主要言語
TypeScript
スター
10
フォーク
2
平均マージ
1日 1時間
マージ済み PR（30日）
23

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

webdriverio/devtools のほかの issue

webdriverio/devtools の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。