Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
133 changes: 105 additions & 28 deletions src/pyretCPOWebEditor.ts
Original file line number Diff line number Diff line change
Expand Up @@ -209,27 +209,38 @@ export function makePyretPane(
const showDefinitions = type === 'cpo';
pane.webview.html = getHtmlForWebview(context, pane.webview, showDefinitions);

function updateWebview() {
pane.webview.postMessage({
protocol: "pyret",
data: {
type: 'setContents',
text: document.getText(),
}
});
}

// Hook up event handlers so that we can synchronize the webview with the text document.
//
// The text document acts as our model, so we have to sync change in the document to our
// editor and sync changes in the editor back to the document.
//
// Remember that a single text document can also be shared between multiple custom
// editors (this happens for example when you split a custom editor)
/*
State/event management for the bidirectional mapping between the
TextDocument (VScode's abstraction) and the webview's CodeMirror instance.

We maintain a queue of edits to apply to the TextDocument, and process them
one after another – they are asynchronous so we need to avoid basic races of
our own creation.

We take a bit of a strong position on edits coming from the webview getting
priority:

- isProcessingEdits is set to true while we are applying edits. If any edits
come in from VScode, we ignore them, counting ours as more important.
- If we get out of sync, or our edits fail to apply, we override everything
with a full replacement of the text that came from the webview with that
edit.

This means that if the user is editing in VScode at the same time as the
webview is trying to make edits, the webview will win. Same for doing
undo/redo events triggered through VScode's menu options that happen at the
same time the user is typing in the CodeMirror view – the webview's version
of things wins.
*/
const editQueue : [vscode.WorkspaceEdit, string][] = [];
let isProcessingEdits = false;

const changeDocumentSubscription = vscode.workspace.onDidChangeTextDocument(e => {
if (e.document.uri.toString() === document.uri.toString()) {
updateWebview();
const hasChanges = e.contentChanges.length > 0;
const isOurDocument = e.document.uri.toString() === document.uri.toString();
if (hasChanges && isOurDocument && !isProcessingEdits) {
updateWebview(e.contentChanges);
}
});

Expand All @@ -238,6 +249,73 @@ export function makePyretPane(
changeDocumentSubscription.dispose();
});

function updateWebview(contentChanges?: readonly vscode.TextDocumentContentChangeEvent[]) {
if(!contentChanges) {
pane.webview.postMessage({
protocol: "pyret",
data: {
type: 'setContents',
text: document.getText(),
}
});
return;
}
for(const change of contentChanges) {
pane.webview.postMessage({
protocol: "pyret",
data: {
type: 'change',
change: {
from: { line: change.range.start.line, ch: change.range.start.character },
to: { line: change.range.end.line, ch: change.range.end.character },
text: change.text.split('\n'),
origin: null
}
}
});
}
}

function enqueueEdit(edit: vscode.WorkspaceEdit, source: string) {
editQueue.push([edit, source]);
processEditQueue();
}
async function processEditQueue() {
function enqueueFullEdit(source : string) {
const fullEdit = new vscode.WorkspaceEdit();
fullEdit.replace(
document.uri,
new vscode.Range(0, 0, document.lineCount, 0),
source);
editQueue.push([fullEdit, source]);
}
if (editQueue.length === 0) { return; }
else if (isProcessingEdits) { return; }
else {
const [edit, source] = editQueue.shift()!;
try {
isProcessingEdits = true;
console.log("Processing edit from ", source);
const ok = await vscode.workspace.applyEdit(edit);
// If something went wrong with the edit, try again but just force the
// whole document contents to match
if(!ok) {
console.error("applyEdit returned false, updating full contents", edit, source);
enqueueFullEdit(source);
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I worry that this line is both here and in the catch block, such that if this line itself causes a problem (somehow), then we immediately try to do it again...

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I hear you, but enqueueFullEdit is pure constructor/builder calls and push. I wish there was a TS annotation for “does not throw”!

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh oh, I misread, and thought the close-brace of enqueueFullEdit included this processing step as well (i.e. enqueue, and immediately try to process if there's anything to process). Yeah, pure constructor calls should be simple enough. So then the only fallible line is the applyEdit call? Or is even that infallible, since you'll get the !ok result from the await? I guess I'm not quite sure what the try/catch is accomplishing...

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I have actually never generated an input that causes this catch to trigger. The docs for applyEdit do not say that it will ever throw (https://code.visualstudio.com/api/references/vscode-api#workspace), just return false. So this may be over-cautious of me. I'm just super paranoid about losing fine-grained edits that bork a file.

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(And other functions have throws documentation if they can, so I think the assumption is that applyEdit does not throw.)

}
}
catch (e) {
console.error("Error applying edit: ", e);
enqueueFullEdit(source);
}
finally {
isProcessingEdits = false;
processEditQueue();
}
}

}

type RPCResponse = { resultType: 'value', result: any, } | { resultType: 'exception', exception: any };
function sendRpcResponse(data: { callbackId: string }, result: RPCResponse) {
pane.webview.postMessage({
Expand Down Expand Up @@ -284,6 +362,10 @@ export function makePyretPane(
const config = vscode.workspace.getConfiguration('pyret-parley');
let context = config.get('defaultContext');
docText = `use context ${context}\n\n`;
const edit = new vscode.WorkspaceEdit();
edit.insert(document.uri, new vscode.Position(0, 0), docText);
await vscode.workspace.applyEdit(edit);
document.save();
}
const initialState = {
definitionsAtLastRun,
Expand All @@ -309,16 +391,11 @@ export function makePyretPane(
case 'change': {
console.log("Got change", e);
const edit = new vscode.WorkspaceEdit();

// Just replace the entire document every time for this example extension.
// A more complete extension should compute minimal edits instead.
// NOTE(joe): we have these on the change events from CodeMirror
edit.replace(
document.uri,
new vscode.Range(0, 0, document.lineCount, 0),
e.state.editorContents)
vscode.workspace.applyEdit(edit);
document.save();
const { from, to, text } = e.data.change;
const range = new vscode.Range(from.line, from.ch, to.line, to.ch);
const newText = text.join('\n');
edit.replace(document.uri, range, newText);
enqueueEdit(edit, e.state.editorContents);
break;
}
default: console.log("Got a message: ", e);
Expand Down