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

Cover LineDiff's CRLF, removal-only and large-diff branches

未关闭 适合新手
#14 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
90/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
活跃
技术栈
csharp
领域
testing

调研方向

阅读 src/Prompuff.Application/Services/LineDiff.cs 中 fallback 和 SplitLines 附近的代码,然后将三个分支测试添加到 tests/Prompuff.Application.Tests/LineDiffTests.cs。运行 dotnet test tests/Prompuff.Application.Tests。当 CRLF、空文本和 2,001 行 fallback 案例验证了指定的变更数量、类型、顺序和行号后,即为完成。

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

描述

good first issue

The History tab's diff comes from LineDiff. Its tests cover additions, edits and identical texts, but three branches have no test:

  • SplitLines turns \r\n into \n, so a body with Windows line endings and the same body with LF endings should show no changes.
  • When the new text is empty or null, every old line is Removed.
  • When the changed middle is bigger than MaxTableCells (4,000,000 cells, so more than about 2,000 lines on each side), it skips the LCS table and lists every old line as removed, then every new line as added.

What to do

Add a test for each branch to LineDiffTests. For the large one, build two texts of 2,001 lines that share no line, such as a0…a2000 and b0…b2000, and check kinds, order and line numbers, not only the counts. Tests only; don't change LineDiff.

Where to look

  • src/Prompuff.Application/Services/LineDiff.cs: the fallback at line 58, SplitLines at line 117.
  • tests/Prompuff.Application.Tests/LineDiffTests.cs.

Done when

  • "a\r\nb" against "a\nb" gives only Unchanged lines, and CountChanges is (0, 0).
  • CountChanges("a\nb", null) is (0, 2), and Compute marks both lines Removed with old line numbers 1 and 2.
  • The large-diff test checks that all 2,001 Removed lines come before the 2,001 Added lines, with the right line numbers.
  • Nothing under src/ changes.

Testing it

dotnet test tests/Prompuff.Application.Tests
主要语言
C#
星标
0
派生
1
平均合并
1 小时 51 分钟
30 天内合并 PR
13

环境准备

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

从这里开始

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

hazeliscoding/prompuff 的其他 Issue

查看 hazeliscoding/prompuff 的全部 Issue

相似的 Issue

更多 C# Issue

把新 issue 发到你的邮箱

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