file-too-long
File exceeds recommended maximum length.
Applies to: C, C#, CPP, Go, H, HPP, JAVA, JavaScript, KT, Python, Ruby, Rust, SCALA, SWIFT, TypeScript
Why this matters
Long files are hard to navigate, understand, and maintain. They often indicate that a file has too many responsibilities. Consider splitting into smaller, focused modules.
Catch it before it ships
pip install stablestack # or: npx stablestackstablestack # scans your project, QUAL009 includedstablestack explain QUAL009False positive in your codebase? Suppress a single line with # noqa: QUAL009
More Code Quality checks
exception-swallowing
Silently swallowed exceptions hide bugs and make debugging hard
QUAL002unnamed-thread
Threads without names are hard to identify in debugging tools
QUAL003complex-tuple
Tuples with 3+ elements are hard to understand - use a dataclass instead
QUAL004mutable-default-argument
Mutable default arguments are shared between calls and cause bugs
QUAL005print-statement
Print statements are typically debugging code that shouldn't be committed
QUAL006todo-comment
TODO/FIXME comments indicate incomplete or problematic code
QUAL007broad-exception
Catching all exceptions hides bugs and makes debugging hard
QUAL008magic-number
Magic numbers make code hard to understand and maintain