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

Collocation: fold src/cli-schema into src/commands/schema, move batch-steps into src/commands/batch

已关闭
#2,679 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
48/100
Issue 类型
重构
描述清晰度
描述清楚
活跃度
活跃
技术栈
typescript
领域
cli, tooling

调研方向

Start by inventorying src/cli-schema, src/commands/schema, src/cli/batch-steps.ts, and the import and documentation paths named in the issue. Rebase onto an up-to-date apex/module-shape-measures after resolving the noted command-suggestions conflict, then run the listed pnpm checks and unit tests. Done means no old path references remain, all checks pass apart from documented unrelated failures, and the coupling and legibility measurements are handed off.

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

描述

Purpose

Split out from #2677: the collocation plan posted there proposes a sequence of src/-touching file moves ("PR A/B/C") derived from the coupling/legibility measures that issue builds. Per a follow-up note, guard 9 on #2677 keeps that issue tooling-only (nothing under src//packages/ changes there), so the moves themselves belong in their own issue(s) rather than under #2677.

This issue tracks "PR A" from the plan: move 1 plus the bundled small move.

Scope

  • Fold src/cli-schema/* (8 production + 8 colocated test files) into src/commands/schema/*. cli-schema is a standalone zone with Q ≈ 0, out/in flow 30, touching 29 of 39 families, and reader-condition legibility in the high-30s/low-40s depending on measurement — the plan's clearest "wrongly-a-family" candidate. It exists only to render the command facets commands/ already owns (#2543 declared that direction).
  • Move src/cli/batch-steps.ts into src/commands/batch/batch-steps.ts (its only relative import and only real importer already live under src/commands/).
  • Pure move, no behavior change: update every import site, the literal owner-files path in src/cli/command-explain.ts, the layering model's zone ranking (folded files resolve to the commands zone by directory, so the standalone cli-schema rank entry is dropped), fallow-baselines/health.json's path-keyed findings, and doc pointers (AGENTS.md, docs/agents/cli-flags.md).

Sequencing note

Per the same follow-up comment, this move should be rebased onto apex/module-shape-measures (the branch implementing #2677's Layer A/B tooling — pnpm coupling / pnpm legibility) so the before/after coupling and legibility numbers are attributable to the move alone, not confounded by the tooling landing separately.

At the time of writing, apex/module-shape-measures (86741f2) is 4 commits behind main, including #2665 (feat(cli): open --wait, flag suggestions, and refusals that name what to run), which also touches src/cli/parser/command-suggestions.ts — one of the files this move touches. Rebasing onto apex/module-shape-measures as-is produces a real conflict there (not just a mechanical one: apex is missing #2665's new suggestFlagFor/flag-suggestion code entirely, so the conflict isn't resolvable by picking a side without either dropping this move's import-path fix for that file or pulling in unrelated feature work). Rebasing cleanly needs apex/module-shape-measures refreshed against current main first.

Acceptance

  • All import sites updated, no stray cli-schema or old batch-steps.ts path references
  • pnpm lint, pnpm typecheck, pnpm format:check, pnpm check:layering, pnpm check:gate-manifest pass
  • pnpm test:unit passes (pre-existing unrelated failures excepted)
  • Rebased onto an up-to-date apex/module-shape-measures, with pnpm coupling before/after numbers in the PR description
  • Base/head SHAs handed off for the pnpm legibility (Jev) before/after measurement, per the offer in https://github.com/callstack/agent-device/issues/2677#issuecomment-5741660420
主要语言
TypeScript
星标
5k
派生
334
平均合并
12 小时 29 分钟
30 天内合并 PR
663

环境准备

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

从这里开始

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

callstack/agent-device 的其他 Issue

查看 callstack/agent-device 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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