Closed natemcmaster closed 2 years ago
The reason is that the cells in a notebook are used as virtual documents. For this reason I actually bend the url to the NotebookDocument for these cells. The hack is not needed for vscode-httpyac. Do you have an example file (test1?) how I can reproduce it?
This error reproduces on any "*.http" file I open, even an empty one. I can reproduce it with a file like
GET http://localhost:3000 HTTP/1.1
Same problem here :-(
Worked some days ago. Don't know what changed
Any news on a fix?
Will have a look at it. Maybe an issue with last vscode update, but this would be 8 days ago. I released vscode-httpyac yesterday but did not change any API conflicting with httpbook.
I think something was changed in the Notebook Editor Api in the latest version. But since I didn't rely on official api here, that was breaking for me. Too bad.
now recognize the Notebook Cells directly from the Uri Scheme vscode-notebook-cell
. Not a stellar performance either, but otherwise I wouldn't get access to environment variables based on the folder structure. My preferred solutions was not accepted (microsoft/vscode#124530)
Fixed by a release of vscode-httpyac in version 5.5.2.
Thanks for the quick update! It is working now for me.
This extension looks really awesome. Unfortunately, I haven't been able to get it working at all. Every time I click "Execute cell" or "Run all", the extension always fails to run the HTTP requests and VS Code shows a notification that says.
If I uninstall the HttpBook extension and use anweber.vscode-httpyac instead, I have no problem getting HTTP requests to work.
Versions
VS Code: 1.68.1 HttpBook extensions: v3.1.1 Httpyac - rest client extension: v5.5.1
More logs
I enabled trace level logging and it produces this