Findings-list renderer wraps long file paths mid-word, causing overlapping/garbled text

Open 💬 2 comments Opened Jul 7, 2026 by andrew-bolin

Description

When the structured code-review findings display renders a finding whose
file:line string is long (e.g. a deeply-nested path like
src/app/widgets/forms/input_validator_helper.py:1234), the path wraps
mid-identifier inside its column (e.g. splitting a filename across
lines mid-word). The [category] tag and the — summary text appear
to be positioned at fixed column offsets that assume the file:line
fits on a single line, so when it wraps instead, they collide with and
overlap the wrapped path text — producing unreadable, garbled output.

Note: this is not a narrow-terminal issue — reproduced in a wide pane
(~200+ columns of dense text visible on the summary lines).

Here's a screenshot of the issue using made-up file names and everyone's favourite filler text

<img width="2521" height="456" alt="Image" src="https://github.com/user-attachments/assets/803df7a0-ffd9-48cf-b40b-784d0b663c77" />

Steps to reproduce

  1. Trigger a code-review findings display (e.g. via /code-review) in a

repo with long/deeply-nested file paths.

  1. Get a finding whose full path/to/file.py:NNN exceeds the renderer's

allotted file/line column width.

  1. Observe the category tag and summary text overlapping the wrapped path.

Expected behavior

Long paths should truncate gracefully with a leading ellipsis so the
filename:line stays intact and readable, e.g.:
.../forms/input_validator_helper.py:1234
instead of wrapping mid-word and colliding with adjacent columns.

Environment

  • OS: Linux
  • Wide terminal pane (not a narrow-width scenario)

🤖 Largely written by Claude 🤖

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗