-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] CLI works but plugin doesn't #4
Comments
I think this occurs when there is a comment after the test name
This should be fixed now. Try the latest |
Okay I just tried the new version. It didn't work at first because I needed to reload vscode. Now I get some action, but still no success. When I click the button, it opens a The output is Successfully parsed YAML. Found YAML Object key testRequest
Found /home/foo/bar/myproject/strest_history.json!
Executing command strest /home/foo/bar/myproject/foo.strest.yml -k testRequest -l /home/foo/bar/myproject/strest_history.json -s /home/foo/bar/myproject/strest_history.json
/bin/sh: 1: strest: not found
error: Error: Command failed: strest /home/foo/bar/myproject/foo.strest.yml -k testRequest -l /home/foo/bar/myproject/strest_history.json -s /home/foo/bar/myproject/strest_history.json
/bin/sh: 1: strest: not found Note it works when I run Remember in that other issue I complained about the need to install the cli tool globally... Well I did do that anyway, with |
I don't think the extension looks anywhere for it. It just tries to execute. The ideal solution is for strest to have an api so the plug-in doesn't use a cli hack for execution |
Same issue here
This path "C:\Users\Vahid\AppData\Local\Programs\Microsoft VS Code\d:\Prog\JWT.strest.yml" shouln't be like this. It's just "d:\Prog\JWT.strest.yml". |
From original issue over here.
latest of everything:
@strest/cli 2.4.0
stREST Client 0.1.1
ubuntu 18.10
vscode 1.31.0
Steps to Reproduce:
foo.strest.yml
fileError is a little popup that says
The text was updated successfully, but these errors were encountered: