Conversation
Deploying codecompanion with
|
| Latest commit: |
33054c8
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://308514f4.codecompanion.pages.dev |
| Branch Preview URL: | https://feat-code-review.codecompanion.pages.dev |
|
Comments Outside DiffThese findings sit on lines the diff does not cover, so they could not be posted inline. Each one leaves this list once its file changes.
|
| local is_new = is_new_scope({ scope = scope, file_diff = file_diff, hunks = opts.group.hunks }) | ||
| -- A single change reads best as the line itself; the scope only earns its place when it summarises more | ||
| if is_new or #opts.group.hunks > 1 then | ||
| label = (is_new and "new " or "in ") .. vim.treesitter.get_node_text(name, opts.source) | ||
| end |
There was a problem hiding this comment.
Single-hunk labels get clipped
For a single hunk inside a function, the checklist now uses the entire first changed line instead of the function name. If that line is long, its label extends past the fixed-width, non-wrapping checklist pane. The identifying text is then clipped, making the row harder to distinguish.
Prompt To Fix With AI
This is a comment left during a code review.
Path: lua/codecompanion/interactions/code_review/checklist.lua
Line: 328-332
Comment:
**Single-hunk labels get clipped**
For a single hunk inside a function, the checklist now uses the entire first changed line instead of the function name. If that line is long, its label extends past the fixed-width, non-wrapping checklist pane. The identifying text is then clipped, making the row harder to distinguish.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
Description
The current code review feature in
CodeCompanionfelt too clunky to use. Using the quick fix to navigate to lines and not being able to see the diff wasn't particularly helpful. This PR introduces a new window and tab feature which allows the user to walk through every edit, accepting or rejecting them as they go.Convenience helpers like being able to go into insert mode and navigate straight to that file and line, as well as being able to use undo against an accepted or rejected hunk, make this hugely improved from a UX perspective.
Supporting Documentation
AI Usage
Claude Code + Fable and Opus 5.5
Related Issue(s)
Screenshots
Checklist
make allto ensure docs are generated, tests pass and StyLua has formatted the code