vscode can not get uri._rootUri. Path any more
See original GitHub issueDoes this issue occur when all extensions are disabled?: Yes
版本: 1.74.0 (system setup) 提交: 5235c6bb189b60b01b1f49062f4ffa42384f8c91 日期: 2022-12-05T16:38:16.075Z Electron: 19.1.8 Chromium: 102.0.5005.167 Node.js: 16.14.2 V8: 10.2.154.15-electron.0 OS: Windows_NT x64 10.0.25262 沙盒化: No
Steps to Reproduce:
click the button from git-repo extension’s icon
we can not get uri._rootUri but uri.Y
?
Issue Analytics
- State:
- Created 9 months ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Target of URI doesn't exist 'package:flutter/material.dart ...
The plugin properly runs "flutter packages get", but VS Code doesn't see the package and does all of the code underlining as if...
Read more >User and Workspace Settings - Visual Studio Code
Be careful since there will be no way to recover your previous setting values. ... You can also have more than one root...
Read more >Remote Development Tips and Tricks - Visual Studio Code
This section includes some tips and tricks for getting the Remote - SSH ... If you do not have a key, run the...
Read more >Managing Extensions in Visual Studio Code
This article explains how to find, install, and manage VS Code extensions from the Visual ... Ignored recommendations will no longer be recommended...
Read more >Visual Studio Code Workspace Trust security
No matter the coding task or problem, there is probably already a good ... via the Workspace Trust editor, and Learn More about...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@lszomoru Thank you for your kindness. After a temporary solution, I try to search for a long-term solution. Finally, after referring to a similar type of VS Code extension, I have fixed the issue that I meet (PR#292). Thank you very much! I don’t have this issue for now.
Maybe a consequence of microsoft/vscode-discussions#257?