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

test(server): finish the CONFIG.md gate: schema rows and types, env read in its own gate, table and anchor integrity

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
55/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
javascript, markdown
领域
testing

调研方向

Start in packages/server/tests/config-supported-keys-docs.test.js and reuse the CONFIG.md parser already there, then read PR #8563 to see how the features inventories and env locations are gated. Add three checks: each CONFIG_SCHEMA key has a row whose type matches, each documented env override is read inside its own flag's gate function, and table column counts and anchor links are valid. Done means all three run in Server Tests and each fails when the mutations in the issue are applied.

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

描述

from-review testing

Follow-up from #7032 / PR #8563. PR #8563 gates the CONFIG.md features inventories, the three env-var locations, and the fail-closed numerals against the real features.<flag> === true gates in src, inside packages/server/tests/config-supported-keys-docs.test.js. Three checks from #7032's original list are still not in the repo:

  • Schema rows. Every CONFIG_SCHEMA key has a CONFIG.md row, and its documented type matches the schema's type.
  • Env override in its own gate. Each documented env override is read in that flag's own gate function, not merely somewhere in src/ (PR #8563 checks only that the literal process.env.<NAME> read exists somewhere).
  • Markdown integrity. Table column counts and anchor links (#7032 reported these as passing at the time).

Acceptance

  • Each check lives in the existing CONFIG.md gate file and reuses its parser. It runs in Server Tests.
  • Each check is proven red by a mutation:
    • a schema key with no row;
    • a row whose type disagrees with the schema;
    • an env override read only outside its gate;
    • a broken table row or anchor.
主要语言
JavaScript
星标
7
派生
1
平均合并
2 小时
30 天内合并 PR
419

环境准备

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

从这里开始

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

blamechris/chroxy 的其他 Issue

查看 blamechris/chroxy 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

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