aboutsummaryrefslogtreecommitdiff
path: root/internal/engine/match_test.go
Commit message (Collapse)AuthorAgeFilesLines
* comments that explain the code, not how it was writtenLukasz Kasprzak2 days1-5/+3
| | | | | | | | | | | | | | | | | | 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.
* gui: name the other copy of a duplicate, and offer to keep this one insteadLukasz Kasprzak2 days1-0/+34
|
* a rule's duplicate check failure shortens the path tooLukasz Kasprzak5 days1-0/+44
|
* duplicate warnings share one formatLukasz Kasprzak5 days1-3/+52
|
* literal braces are text, not placeholders, for containment and walk exclusionLukasz Kasprzak5 days1-0/+2
|
* krino: duplicates are found, never deletedLukasz Kasprzak5 days1-1/+1
| | | | | | | | | A rule combining (duplicate) with a delete action is refused at load, and a file that is a duplicate under any duplicate scope its directory uses gets no delete step from any rule: the plan shows it skipped and the chain continues. A failed duplicate check blocks the delete too. Tests cover (matched), another rule's own condition, a test evaluation skipped, two scopes and a failed check, each checking every copy is still on disk.
* krino: matching — scan, ignore, conditions, extraction, duplicates, ↵Lukasz Kasprzak8 days1-0/+367
explain, dry run