davsclaus opened a new pull request, #27188:
URL: https://github.com/apache/camel/pull/27188

   _Claude Code on behalf of davsclaus_
   
   **Stacked on #27187** (quick fixes): it targets that branch, and moves to 
`main` once #27187 is merged.
   
   The check finds the problem, the human decides, and the AI writes the fix. 
On a line with a problem in the Source editor, **Shift+F8** does three things:
   1. It saves the file as it is in the editor, since the AI is about to change 
it.
   2. It leaves edit mode, so the editor shows what the AI sees.
   3. It opens the AI panel with the question **in its input**: the file 
(relative to the project, as the AI's file tools want it), the line, the 
problem, its text, and to fix only that with `camel_edit_file` and then 
`camel_validate_source`.
   
   Nothing is sent until the user presses Enter, so they can change the 
question first.
   
   The Error panel shows `Shift+F9 fix: ... Shift+F8 fix with AI`, and the 
footer shows both. The global F8 (AI panel) now leaves Shift+F8 to the editor; 
F3, F6 and F8 are global keys.
   
   ### Tested live
   The panel opened with the question for `seda: Unknown option 'siz'` on line 
12. A local model (qwen3.6 via Ollama) fixed it, which closes the loop.
   
   It also showed something for a follow-up: `camel_edit_file` and 
`camel_write_file` refuse a file with *any* problem, so the model also had to 
fix the unrelated `to` → `toD` on another line before it could write. They 
should only refuse the problems a write introduces.
   
   New tests in `SourceQuickFixTest`: the question (`AiFixPrompt`), and 
Shift+F8 saving the unsaved edit, leaving edit mode and asking with the right 
line. The full TUI module (1460) passes.
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to