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

usabl docs: add a whole-app mode that documents every in-scope surface

未关闭
#114 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
52/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
冷清
技术栈
playwright, typescript

调研方向

Start by reading the usabl docs command path and tracing how it selects in-scope surfaces from a run and git status. The issue identifies the renderer’s three honesty states as already working, so focus on what the generator feeds it. Done means a whole-app mode includes every in-scope surface independent of git status while preserving honest empty results, receipt evidence requirements, and exit 0 without minting a verdict.

由索引模型根据 Issue 内容生成。

描述

area: docs enhancement

Background

usabl docs projects documentation artifacts (alt-text manifest, announcement snippets, keyboard paths) from a run. Today the run it projects from is scoped the same way the gate scopes work: to the surfaces the current change actually touched. That is the right default for the gate, because the gate only judges what changed. It is a surprising default for documentation, where a reader usually wants the whole application described, not just the diff.

Current behavior

On a clean working tree, a run reaches few or no surfaces, so usabl docs (and usabl docs --html) can produce little or nothing. That is honest, but it is easy to mistake for a bug: "I asked for the docs and got an almost empty page."

Proposed behavior

Add a whole-app documentation mode that documents every in-scope surface, independent of git status, so a reader can generate a full accessibility document for the application on demand.

Keep the honesty invariant intact:

  • A clean tree with nothing to prove should still yield an honest idle or empty result, clearly labelled, never a fabricated verdict.
  • Whole-app mode is a generator like the current command: it always exits 0 and mints no verdict. Only surfaces that reached a minted receipt with per-entry evidence may read as verified; everything else stays an expectation or an observation, exactly as in the per-change mode.

Notes

Discovered while building usabl docs --html. The renderer already distinguishes the three honesty states correctly; this issue is about widening what the generator feeds it, not about the rendering.

主要语言
TypeScript
星标
0
派生
0
平均合并
2 小时 48 分钟
30 天内合并 PR
8

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 有 Pull Request 模板
  • 没有贡献指南

从这里开始

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

usabl-dev/usabl 的其他 Issue

查看 usabl-dev/usabl 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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