API endpoints can't be edited using VS Vode
Editing an API endpoint using VS Code and PSU Extension doesn't work. When creating an API endpoint I tried supplying a Path: testendpoint.ps1. However in vs code the file it seems to be editing is not the file live on powershell universal. How is this supposed to work?
All Comments (3)
Hello scheived,
Thank you for the additional report.
This appears to match the behavior you previously documented in case 55738, where editing a file-backed API endpoint through the VS Code extension targets a different file path than the one PowerShell Universal actually uses for the endpoint.
For endpoints created with `New-PSUEndpoint -Path`, the path is expected to be relative to the `.universal` directory. Based on what you are seeing, we need to verify whether the VS Code extension is resolving that path differently when using the Edit action.
We already have the detailed reproduction information from your previous report, so there is no need to provide it again. We will use that scenario for our internal reproduction and continue the investigation from there.
References:
https://docs.devolutions.net/powershell-universal/api/endpoints
https://forum.devolutions.net/topics/55738/vs-code-extension-editing-a-filebacked-api-endpoint-saves-to-the-wrong
Best regards,
Ruben Tapia
One additional note: we are also tracking related VS Code extension behavior in case 55651. That investigation has reproduced issues with the extension and bug reproduction steps have already been submitted upstream.
We are going to compare the API endpoint editing behavior reported here and in 55738 against those findings to determine whether they share the same underlying issue or need to be tracked separately.
References:
https://forum.devolutions.net/topics/55651/vscode-extension-for-powershell-universal-anybody-using-it
https://forum.devolutions.net/topics/55738/vs-code-extension-editing-a-filebacked-api-endpoint-saves-to-the-wrong
Best regards,
Ruben Tapia
Hello scheived,
Just a quick update. Cases #55738 and #55846 have now been escalated together for further review, since both reports describe the same file-backed API endpoint editing behavior in the VS Code extension.
We have included the path-resolution details and the relationship between the two reports so the issue can be reviewed as a single investigation rather than duplicated.
We will update the forum once we have additional findings.
Best regards,
Ruben Tapia