When an edit or a write waits for your approval, the Oda extension opens it in VS Code's diff editor as a proposal: the file as it stands next to the file with Oda's change. You review the change block by block, edit the copy if you want a different result, and accept or reject it; your answer goes back to the chat. Only edit and write approvals are offered to the editor; every other approval still asks in the chat. What the extension adds to your editor is on The Oda extension for VS Code.
DataMind Oda removes these lines. for a block that takes lines away, or DataMind Oda proposes this change. for one that changes or adds them.Reject this change with instructions and the placeholder Tell DataMind Oda what to do instead. Sending the reply rejects that block with your note.Reject with instructions, with the prompt Tell Oda what to do instead.A proposal with more than 100 changed blocks is reviewed as a whole file: the per-block comment threads are not created. Everything else works the same, and you accept or reject the change as one.
Allow Edits for This Chat applies to a chat in Read only access. What each mode allows is on Permission presets.If VS Code does not apply the review in time, Oda reports VS Code did not apply the review. The request still waits, so answer it again, for example from the chat's approval card.
Messages from other parts of Oda are in Troubleshooting.
In a changed block's thread (Accept this change and Reject this change), from the diff's title bar or the Command Palette (Accept Proposed Change, Reject Proposed Change and Reject with Instructions…), or from the right-click menu on a change in the editor (Accept Change at Cursor and Reject Change at Cursor).
The left side is the file as it stands; the right side is a copy of the file with Oda's change, and you can edit it before you decide. When the change creates a file, the left side is empty.
Your version is written to the file, and Oda is told to read the file again before it continues.
Reply in the block's thread: the box carries the prompt Reject this change with instructions and the placeholder Tell DataMind Oda what to do instead. Or choose Reject with Instructions…, which opens a box titled Reject with instructions with the prompt Tell Oda what to do instead. Your note is passed on to Oda with the change it concerns.
An edit or a write that waits for your approval. It opens in the diff editor as a review, and your answer goes back to the chat. Every other approval still asks in the chat.
The diff has more than 100 changed blocks. Over that limit a proposal is reviewed as a whole file and the per-block threads are not created; accept or reject it as one change. Everything else works the same.
It is offered for a chat in Read Only access, where file changes are stopped: choosing it lets Oda apply edits in that chat. In any other access mode the action reports Allow Edits for This Chat applies to a chat in Read only access. Permission presets covers the modes.
No. A rejected change is not written to the file. With instructions, your note tells Oda what to do instead.
Yes. The chat keeps its own approval card for the same request, and answering in either place closes the other. If you reviewed the change in the editor first, the card says so, and Allow once applies the version you reviewed. Approvals covers the card.
It means the change was reviewed in VS Code's diff editor. Allow once on the card then applies the version you reviewed there; the note reads You reviewed this change in VS Code.
VS Code did not apply the review mean?The editor did not apply your reviewed version to the file in time, so the answer failed. The request still waits: answer it again, for example from the chat's approval card.
Nothing is written to the file while the request waits. Closing the diff does not answer the request: it still waits, and you answer it from the chat's approval card (Approvals).