Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Hardcoded `vscode-vfs` dependency

See original GitHub issue

In some places:

Should imho not hardcode because it originates from an extension. Can rather use IPathService.defaultUriScheme

Issue Analytics

State:
Created 2 years ago
Comments:6 (6 by maintainers)

Top GitHub Comments

1reaction

chrmarticommented, Aug 25, 2021

That’s in an extension which doesn’t have access to IPathService. We could check the first workspace folder’s URI scheme (if it is not an empty window).

0reactions

sbattencommented, Oct 4, 2021

our hardcoding is actually a workaround for not having any api for this, but we also do not have a major reason to generalize the API at this time. suggestions welcome

Top Results From Across the Web

Virtual Workspaces | Visual Studio Code Extension API

Run your extension against a virtual workspace. Install the GitHub Repositories extension and run the Open GitHub Repository... command from the Command Palette ......

Remote Repositories extension for Visual Studio Code

Remotely browse and edit a source control repository from within Visual Studio Code.

Managing Java Projects in VS Code

Lightweight Mode, Maven Support, Java Package and Dependency Management in Visual Studio Code.

Supporting Remote Development and GitHub Codespaces

A guide to adding Visual Studio Code Remote Development and GitHub ... Extension dependencies work fine when all the extensions are running locally...

Source Control with Git in Visual Studio Code

Tip: You can open VS Code in a sub-directory of a Git repository. VS Code's Git services will still work as usual, showing...