14.3–15.4: quality ratchet — edge-parameter tests, coverage floors, missing_docs
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 35/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- rust
- 领域
- build-system, testing
调研方向
Start with the named test files, crates/compose/src/effects.rs and crates/io/src/psd.rs, then inspect the coverage configuration and crate manifests or crate roots for the coverage floors and missing_docs settings. Measure coverage on the exact SHA before proposing floor changes, and evaluate each remaining crate for missing documentation. Done means all four items are completed or recorded as not applicable with reasons, with no weakened gates or unverified baseline entries.
由索引模型根据 Issue 内容生成。
描述
Phase 14–15 quality ratchet: the coverage and documentation gates are only partially enforced, so regressions can pass unnoticed.
Work
- 14.3 —
crates/compose/src/effects.rsedge-parameter tests. Audit the existing 40 tests against the out-of-domain parameter paths and add the gaps. - 14.4 —
crates/io/src/psd.rsmalformed-header tests. The current set covers truncation at every prefix, an oversized colour-mode section, a negative width and unsupported bit depths; extend to the remaining malformed-header shapes the reader can be handed. - 14.5 — re-bless the coverage floors and record per-crate coverage snapshots. The floor must move only in the direction the ratchet allows, and the re-bless must be evidence-backed, not a number typed to go green.
- 15.4 —
missing_docsevaluation: it is currentlydeny(missing_docs)oncrates/geomandcrates/coloronly. Evaluate the remaining crates and record which qualify, then enable per crate.
Acceptance
- Each of the four items has either landed with tests, or is recorded as not-applicable with a reason.
- The coverage floors are re-blessed from measured coverage on the exact SHA.
- No gate is weakened to reach green, and no baseline entry is added without verifying the finding is a false positive.
Tracking: tasks #154, #155, #156, #157, #184.
- 主要语言
- Rust
- 星标
- 11
- 派生
- 1
- 平均合并
- 9 小时 48 分钟
- 30 天内合并 PR
- 13
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
aliasfoxkde/FireCraft 的其他 Issue
-
documentation release
难度 2/5 1-3 小时 新手友好度 68/100
aliasfoxkde/FireCraft#58 ·
维护者通常 1 天内回复
-
release
难度 4/5 3-5 天 新手友好度 54/100
aliasfoxkde/FireCraft#81 ·
维护者通常 1 天内回复
-
enhancement parity
难度 4/5 3-5 天 新手友好度 48/100
aliasfoxkde/FireCraft#79 ·
维护者通常 1 天内回复
-
enhancement
难度 5/5 一周以上 新手友好度 38/100
aliasfoxkde/FireCraft#78 ·
维护者通常 1 天内回复
-
enhancement
难度 4/5 3-5 天 新手友好度 42/100
aliasfoxkde/FireCraft#77 ·
维护者通常 1 天内回复
查看 aliasfoxkde/FireCraft 的全部 Issue
相似的 Issue
-
agent-self
难度 2/5 1-3 小时 新手友好度 84/100
yologdev/yoyo-evolve#1176 ·
-
难度 2/5 1-3 小时 新手友好度 67/100
Richard-Zhang1019/Crossbow#431 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 86/100
saschanaz/jxl-winthumb#69 ·
-
ready
难度 1/5 1 小时以内 新手友好度 88/100
TusanHomichi/PSIV#504 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复