For now the project is badly covered by the tests. It can be greatly improved.
Contributor guide
Tech stack
rust
Domain
clitesting
Issue type
test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
unclear
Prerequisites
Rust programming basicsfamiliarity with cargo testunderstanding of lsd project structure
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Examine the current test suite in the tests/ directory. Use cargo tarpaulin or similar to identify untested code. Prioritize core functionality like file output and sorting. Check issue comments for any specific areas mentioned.
