The Code view, in a project’s Metrics tab, lets you walk your repository’s directory tree with per-file metrics. It’s the fastest way to find which files in the project carry the most risk.Documentation Index
Fetch the complete documentation index at: https://docs.qlty.sh/llms.txt
Use this file to discover all available pages before exploring further.
Sub-views
The Code area has three sub-tabs:- Tree — Hierarchical view that mirrors your repository’s directory layout. Click a folder to drill into it; click a file to open its metrics page. Each row shows the path’s aggregated size, complexity, coverage, and maintainability grade.
- List — Flat list of every file in the tracked branch with the same columns as Tree, but sortable across the whole project. Use this when you want to find the most complex or worst-rated file regardless of where it lives.
- Unformatted Files — Subset showing only files that Qlty’s auto-formatters would rewrite (i.e. files with one or more
fmt-level issues raised by a formatter plugin). Useful for working through a formatting backlog one file at a time.
Columns
Every row displays:- Type — folder or file icon.
- File — the path, with a clickable link to either the deeper folder view or the per-file metrics page.
- Size — code lines, expressed as a relative “shirt size” (S/M/L/XL) for quick scanning.
- Complexity — cognitive complexity score for the file or aggregated for the folder.
- Coverage — line coverage percentage (only when coverage data has been uploaded).
- Maintainability grade — A–F rating combining smells, complexity, and duplication signals.
When you click into a file
The per-file metrics page shows:- The file’s headline grade and individual metric values.
- The list of open issues affecting the file.
- Per-line coverage hits when coverage data exists.