Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Generate the adapter capability matrix instead of maintaining three by hand

未关闭
  • 哪里不对？
#402 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
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 小时
30 天内合并 PR
23

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

webdriverio/devtools 的其他 Issue

查看 webdriverio/devtools 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。