Editing scripts.ps1 fails with error

[JessePeden]

Trying to edit scripts.ps1 through the PSU VS Code extension, using the button at the top of the AUTOMATION frame, results in the following error:

Error running command powershell-universal.openScriptConfigFile: cannot open file:///c%3A/ProgramData/UniversalAutomation/Repository/.universal/scripts.ps1. Detail: Unable to read file 'c:\ProgramData\UniversalAutomation\Repository\.universal\scripts.ps1' (Error: Unable to resolve nonexistent file 'c:\ProgramData\UniversalAutomation\Repository\.universal\scripts.ps1'). This is likely caused by the extension that contributes powershell-universal.openScriptConfigFile.

The same button in the other frames (such as for APIS) works as it should.

Oddly enough, opening the scripts.ps1 file from the CONFIGURATION frame and navigating to the .universal sub-folder (the same path that should be used to open the scripts.ps1 file with the aforementioned button) works just fine.

[JessePeden]

@adamdriscoll This is still an issue with the most recent release of the VS Code extension, fyi.