You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tricky part was to not invalidate the cache twice for the same change.
Lots of LSP lifecycle messages (onDidCreateFiles, onDidRenameFiles,
onDidDeleteFiles, onDidSaveTextDocument) were fired before the
onDidChangeWatchedFile events.
Had to do a little trick to avoid invalidating the cache twice for
those.
Fixes#692
Tricky part was to not invalidate the cache twice for the same change.
Lots of LSP lifecycle messages (onDidCreateFiles, onDidRenameFiles,
onDidDeleteFiles, onDidSaveTextDocument) were fired before the
onDidChangeWatchedFile events.
Had to do a little trick to avoid invalidating the cache twice for
those.
Fixes#692
Tricky part was to not invalidate the cache twice for the same change.
Lots of LSP lifecycle messages (onDidCreateFiles, onDidRenameFiles,
onDidDeleteFiles, onDidSaveTextDocument) were fired before the
onDidChangeWatchedFile events.
Had to do a little trick to avoid invalidating the cache twice for
those.
Fixes#692
Describe the bug
Git operations change files in the workspace without shooting textDocument/did{Open,Change,Save,Close} lifecycle notifications.
This means that if you revert changes and do a rename, then the internal representation of preloaded files might be off.
Expected behaviour
When files are modified "under our feet", we need to sync them to the document manager with updated values
Actual behaviour
Stale values are kept around
The text was updated successfully, but these errors were encountered: