Commit Graph

2 Commits

Author SHA1 Message Date
Steve Yegge
2c4c7dddcd docs: Update LINTING.md baseline to reflect test coverage growth
Update documented baseline from ~100 to ~200 linting issues. The increase
is due to significant test coverage additions between Oct 12-14:
- Collision resolution tests (1100+ lines)
- Auto-flush feature tests (300+ lines)

All new warnings follow the same idiomatic patterns (deferred cleanup
without error checks). Updated breakdown:
- errcheck: 73 → 159 (test cleanup operations)
- gosec: 7 → 19 (test file paths, validated SQL)
- revive: 17 → 21 (Cobra interface requirements)
- gocyclo: 0 → 1 (comprehensive integration test)
- goconst: 1 → 2 (test string constants)

All warnings remain legitimate false positives. No change in code quality
or security posture.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-14 13:28:57 -07:00
Steve Yegge
2c7708eaa7 Address remaining golangci-lint findings
- Add package comment to cmd/bd/dep.go
- Change directory permissions from 0755 to 0750 in init.go
- Simplify getNextID signature (remove unused error return)
- Configure golangci-lint exclusions for false positives
- Document linting policy in LINTING.md

The remaining ~100 lint warnings are documented false positives:
- 73 errcheck: deferred cleanup (idiomatic Go)
- 17 revive: Cobra interface requirements and naming choices
- 7 gosec: false positives on validated SQL and user file paths
- 2 dupl: acceptable test code duplication
- 1 goconst: test constant repetition

See LINTING.md for full rationale. Contributors should focus on
avoiding NEW issues rather than the documented baseline.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-12 09:48:22 -07:00