Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extensions do not work with RemoteFS #91

Open
ogcsantos opened this issue Feb 22, 2021 · 2 comments
Open

Extensions do not work with RemoteFS #91

ogcsantos opened this issue Feb 22, 2021 · 2 comments

Comments

@ogcsantos
Copy link

well, I'm having problems using the formatter or Intelephense of some language in my code using RemoteFS, I just can't, and below it shows an error of one of the extensions that I use outside of RemoteFS.

image

@e-u-shapovalov
Copy link

Describe the bug
PHP code intelligence for Visual Studio Code don't work via Remote File System for VS Code

To Reproduce
Open php file via Remote File System for VS Code

Screenshots
2021-04-05_22-09-36

Platform and version
OS WIN10 and Intelephense version v1.6.3.

@PeterWone
Copy link

PeterWone commented Sep 14, 2021

Extensions that don't work with remote filesystems are generally written incorrectly (like mine, which I am currently fixing in this respect).

They import fs and use the node filesystem methods. What they should do is use the filesystem object provided by the vcode API, and instead of using filepath strings they should use the vscode.Uri objects returned by most of the UI interaction events. These URIs are annotated as to the filesystem in which they should be resolved. If you use the methods on the file system object available from vscode.workspace.fs you have access to both local and remote filesystems.

If you have a particular extension in mind raise an issue on the pertinent repo and tell the author to read this comment (you should be able to copy a direct link) and then they should refer to this documentation link https://code.visualstudio.com/api/references/vscode-api#FileSystem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants