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

The manual's tab-row examples show the wrong spacing after home

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
78/100
Issue 类型
文档
描述清晰度
描述清楚
活跃度
活跃
技术栈
go
领域
cli, documentation

调研方向

Start with the schematic rows at internal/manual/chat/screen.md:103 and internal/manual/chat/home.md:592, then compare them with the rendering in internal/tui3/hometabs.go. Run the stated codeaf manual query and capture the first codeaf chat row at the specified terminal width. Done means both manual answers accurately match the captured spacing or clearly label the examples as schematic, with the focused documentation check covering the shared sample grammar.

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

描述

area:chat bug good first issue sev:papercut

Seen on dev@debffabf6. Surfaced while verifying #1424; not introduced by it.

What happened

The sample tab rows in screen.md and home.md show spacing after home that differs from the actual row after #1424's alignment change. They are presented as visual examples, so the cell positions are part of the instruction.

Replication

Deterministic (no model). Run codeaf manual "how are conversation tabs laid out", then capture the first row of codeaf chat on a standard-width terminal and compare the spaces following home. The two manual samples differ from the captured row.

Where

internal/manual/chat/screen.md:103 and internal/manual/chat/home.md:592 at dev@debffabf6 contain the schematic rows; the current rendering is in internal/tui3/hometabs.go.

The fix

Make the examples accurately show the current row's spacing, or label them explicitly as schematic without implying exact cells.

Acceptance

  • e2e: both codeaf manual answers show a tab sample whose home spacing matches a captured codeaf chat row at the stated width.
  • Unit: a focused documentation check protects the shared sample grammar.
  • Record the former examples in invalidates.
主要语言
Go
星标
115
派生
14
平均合并
9 小时 35 分钟
30 天内合并 PR
752

环境准备

我们还没有检查这个项目的环境配置文件。先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

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

Agent-Field/CodeAF 的其他 Issue

查看 Agent-Field/CodeAF 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

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