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
Hi, I've implemented my own LocalFileSystemProvider to use a real filesystem provider to work with real files in disk. Below wrapperConfig I'm not setting the codeResources under editorAppConfig since I want to post init() later in UI to load a specific file.
Now when I call init() it starts with a inmemory model and after calling await vscode.workspace.openTextDocument(uri);. And then start(). It continues to work with inmemory model only all changes are passed to LSP for the inmemory model and not the URI file I loaded with openTextDocument.
So my query is shouldn't it load the contents from openTextDocument onto the editor model and further changes be tracked on it?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi, I've implemented my own LocalFileSystemProvider to use a real filesystem provider to work with real files in disk. Below wrapperConfig I'm not setting the
codeResources
undereditorAppConfig
since I want to post init() later in UI to load a specific file.Now when I call init() it starts with a inmemory model and after calling
await vscode.workspace.openTextDocument(uri);
. And then start(). It continues to work with inmemory model only all changes are passed to LSP for the inmemory model and not the URI file I loaded with openTextDocument.So my query is shouldn't it load the contents from openTextDocument onto the editor model and further changes be tracked on it?
WrapperConfig:
Beta Was this translation helpful? Give feedback.
All reactions