A way to apply edits on the client side
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading FileChangeRequestApprovalParams and the item/fileChange/patchUpdated flow described in the issue. Clarify how partial acceptance, patch amendment, and client-applied proposal mode should interact with the existing accept, acceptForSession, decline, and cancel decisions. Done means an agreed protocol design that lets the Eclipse client apply changes itself.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100