Replies: 4 comments
-
I currently use a simple .vscode/tasks.json file with the following content: {
// See https://go.microsoft.com/fwlink/?LinkId=733558
// for the documentation about the tasks.json format
"version": "2.0.0",
"tasks": [
{
"label": "shellspec failure",
"type": "shell",
"command": "${workspaceFolder}/shellspec -f failures ${relativeFile}",
"problemMatcher": [
"$msCompile"
]
},
{
"label": "shellspec",
"type": "shell",
"command": "${workspaceFolder}/shellspec ${relativeFile}",
"problemMatcher": [
"$msCompile"
],
"group": {
"kind": "build",
"isDefault": true
}
},
{
"label": "shellspec with trace ",
"type": "shell",
"command": "${workspaceFolder}/shellspec -x ${relativeFile}",
"problemMatcher": [
"$msCompile"
]
}
]
} and it works ! |
Beta Was this translation helpful? Give feedback.
-
Wow! thanks a lot. I use vscode, but I'm not familiar with how to customize. I noticed that the output of the syntax check is also better to be the same as the failures formatter. I'd also like a specfile syntax highlighter. |
Beta Was this translation helpful? Give feedback.
-
Another benefit of pursuing a standardized implementation of Gherkin is that users would get all the accompanying tooling around Gherkin/Cucumber. |
Beta Was this translation helpful? Give feedback.
-
I might be late to the game, but I am working on a vscode extension for Shellspec (I do not have experience with that, so it is not the most efficient and nicely coded, but it is coming along nicely). However, there are some things I am having trouble with. Any help is appreciated:
|
Beta Was this translation helpful? Give feedback.
-
I want it. 🤩
Beta Was this translation helpful? Give feedback.
All reactions