New Project experience doesn't open project folder correctly in some cases #390
Labels
Issue-Bug
A bug to squash.
Comments
|
Ultimately depends on PowerShellOrg/Plaster#218 being wired up through Editor Services. |
daviwil
added a commit
to PowerShell/PowerShellEditorServices
that referenced
this issue
Jan 18, 2017
This change fixes PowerShell/vscode-powershell#390 which states that the New Project experience in VS Code doesn't work well with project paths which use characters like '~' to represent the home directory. This change causes the fully resolved DestinationPath of the template creation to be passed back to the editor so that it can be opened.
daviwil
added a commit
to PowerShell/PowerShellEditorServices
that referenced
this issue
Jan 18, 2017
This change fixes PowerShell/vscode-powershell#390 which states that the New Project experience in VS Code doesn't work well with project paths which use characters like '~' to represent the home directory. This change causes the fully resolved DestinationPath of the template creation to be passed back to the editor so that it can be opened.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Destination paths like the following don't open correctly:
~/MyNewModule$HOME/MyNewModuleWe should resolve these paths in the language server and send back the full path to the new workspace so that VS Code doesn't need to resolve the path (especially in the case of using PowerShell variables like
$HOME).The text was updated successfully, but these errors were encountered: