-
Notifications
You must be signed in to change notification settings - Fork 0
cleanup opportunities
Douwe de Vries edited this page Jul 1, 2026
·
2 revisions
This section captures cleanup areas found during the wiki scan. It is a reference list, not a mandate to refactor immediately.
No tracked source or documentation matches were reported for TODO, FIXME, or HACK in the shared cleanup scan. The main cleanup opportunities are structural:
- Large integration test files that could be split carefully.
- Large frontend styling and packaging scripts that need guarded refactors.
- Dependency areas to watch during normal maintenance, without claiming any package is outdated.
| Page | What it covers |
|---|---|
| Complexity hotspots | Large files and cautions for refactoring tests, comparison logic, CSS, and packaging scripts. |
| Dependency freshness | Current dependency snapshot and areas to monitor during upgrades. |
- Prefer behavior-preserving splits over broad rewrites.
- Move shared fixtures before splitting large test files.
- Keep snapshot, pair-order, transport, and package metadata contracts covered while refactoring.
- Run the validation commands from testing before treating cleanup as complete.
| File | Cleanup relevance |
|---|---|
/Users/vriesd/projects/csv-align/tests/comparison_engine_integration.rs |
Largest Rust integration test file. |
/Users/vriesd/projects/csv-align/frontend/src/features/results/resultsSurface.css |
Largest frontend styling surface. |
/Users/vriesd/projects/csv-align/src/comparison/engine.rs |
Core comparison implementation with many invariants. |
/Users/vriesd/projects/csv-align/scripts/validate_linux_deb_metadata.py |
Large packaging validator with security-sensitive extraction logic. |
/Users/vriesd/projects/csv-align/scripts/build_apt_repository.py |
Large repository builder with signing and package-generation behavior. |