aboutsummaryrefslogtreecommitdiff
path: root/cmd/krino/commands_test.go
diff options
context:
space:
mode:
authorLukasz Kasprzak <lukas@labunix.xyz>2026-09-17 12:11:42 +0200
committerLukasz Kasprzak <lukas@labunix.xyz>2026-09-17 12:11:42 +0200
commitbddbd74e4a73e8e32bcf648efd1cac5655f6d0cd (patch)
tree187e6a1fb722d9ab97d2076f69f997f5d371e943 /cmd/krino/commands_test.go
parentcd7425b81f963a948f0abe7df3f9e58e190c2b78 (diff)
downloadkrino-bddbd74e4a73e8e32bcf648efd1cac5655f6d0cd.tar.gz
krino-bddbd74e4a73e8e32bcf648efd1cac5655f6d0cd.zip
comments that explain the code, not how it was written
About 340 comments cited the development process: task and plan numbers, fix waves, rulings, reviewers, and the author in the third person with a date. None of that exists outside the work itself, so to a reader it pointed at nothing. Each one now states the engineering reason it was standing in front of; where a comment was provenance and nothing else, it is gone. References to docs/design.md and docs/gui-design.md by section stay: both ship with the repository. The design documents lose their amendment diaries - CHANGELOG.md is that record - and the GUI's says plainly that the window has gone further than the document. Only comments changed. Every .go file was parsed and its code printed with comments stripped, before and after: the two hashes are identical across all 175 files.
Diffstat (limited to 'cmd/krino/commands_test.go')
-rw-r--r--cmd/krino/commands_test.go15
1 files changed, 7 insertions, 8 deletions
diff --git a/cmd/krino/commands_test.go b/cmd/krino/commands_test.go
index b8364e6..f681a0f 100644
--- a/cmd/krino/commands_test.go
+++ b/cmd/krino/commands_test.go
@@ -10,12 +10,11 @@ import (
)
// home gives each test its own HOME with no XDG overrides, and points the
-// package's stdin seam at something guaranteed non-terminal (fix round
-// 2026-09-12/item 4): every test that reaches cmdSort's terminal check or
-// the interactive review must not depend on what the ambient test binary's
-// stdin happens to be - if that were ever a real terminal, such a test
-// would silently fall through to the interactive prompt and block on a
-// keypress instead of failing.
+// package's stdin seam at something guaranteed non-terminal: every test
+// that reaches cmdSort's terminal check or the interactive review must not
+// depend on what the ambient test binary's stdin happens to be - if that
+// were ever a real terminal, such a test would silently fall through to
+// the interactive prompt and block on a keypress instead of failing.
func home(t *testing.T) string {
t.Helper()
h := t.TempDir()
@@ -78,8 +77,8 @@ func TestInitNewCheck(t *testing.T) {
}
}
-// TestConfigFlagExpandsTilde is item B: -c=~/... is not expanded by the
-// shell (the ~ comes after =), so krino must expand it itself.
+// TestConfigFlagExpandsTilde: -c=~/... is not expanded by the shell (the ~
+// comes after =), so krino must expand it itself.
func TestConfigFlagExpandsTilde(t *testing.T) {
h := home(t)
cwd := t.TempDir()