vscode-perforce
vscode-perforce copied to clipboard
stef-levesque
Watch for file status change
When a file is changed and then committed using p4v, the file in the editor still have change marks:
They don't go away even if I close the file and reopen. They are removed only when I close and reopen vscode.
This is related to the quick diff editor gutter decorations, computed by VS Code itself.
@joaomoreno any idea why the editor would used a cached version of the 'Original' resource?
@stef-levesque As part of the TextDocumentContentProvider interface, you need to ping Code that the original resource has changed, by firing the onDidChange event. It appears the extension isn't firing it ever. 👍
Is there any workaround for this in the mean time, other than reopening vscode?
