What variant of Codex are you using?
Codex with our Eclipse IDE plugin (codexide.org)
What feature would you like to see?
FileChangeRequestApprovalParams only contains itemId, reason, grantRoot, threadId, turnId, but not the paths or the patch.
You have to correlate with item/fileChange/patchUpdated. The decisions are accept / acceptForSession / decline / cancel.
What is missing: partial acceptance (hunk by hunk), amending the patch before application, and above all a "proposal" mode where the client applies it itself.
This would allow going through Eclipse's undo, file, and Java refactorings, instead of writing under Eclipse's nose and forcing a rescan.
Additional information
No response
What variant of Codex are you using?
Codex with our Eclipse IDE plugin (codexide.org)
What feature would you like to see?
FileChangeRequestApprovalParams only contains itemId, reason, grantRoot, threadId, turnId, but not the paths or the patch.
You have to correlate with item/fileChange/patchUpdated. The decisions are accept / acceptForSession / decline / cancel.
What is missing: partial acceptance (hunk by hunk), amending the patch before application, and above all a "proposal" mode where the client applies it itself.
This would allow going through Eclipse's undo, file, and Java refactorings, instead of writing under Eclipse's nose and forcing a rescan.
Additional information
No response