You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just trying to throw things at the wall and see what would stick, I customized the command used in my settings.json so that it would add the .cmd extension to it, and that does cause it to at least no longer return the error running the command.
But it doesn't return any issues, even if there are issues reported running gherkin-lint directly. I noticed the $file path generated always seems to have a / at the beginning, and I'm thinking perhaps that's causing a problem?
If I run the command exactly as it is laid out in the output directly in my terminal, but without that slash at the beginning of the file path, gherkin-lint runs successfully and returns the list of issues:
gherkin-lint.cmd --config c:\Projects\AyaHealthcare\Applications\QaAutomation.gherkin-lintrc --format json c:/Projects/AyaHealthcare/Applications/QaAutomation/cypress/e2e/smoke/travelx/ticketing-smoke-tests.feature
[{"filePath":"c:\Projects\AyaHealthcare\Applications\QaAutomation\cypress\e2e\smoke\travelx\ticketing-smoke-tests.feature","errors":[{"message":"Missing Feature name","rule":"no-unnamed-features","line":1},{"message":"Forbidden tag @Focus on Scenario","rule":"no-restricted-tags","line":3}]}]
The text was updated successfully, but these errors were encountered:
I am using this extension on VS Code in Windows with gherkin-lint and am having some issues. If I look at the output, I get something like this:
Just trying to throw things at the wall and see what would stick, I customized the command used in my settings.json so that it would add the .cmd extension to it, and that does cause it to at least no longer return the error running the command.
But it doesn't return any issues, even if there are issues reported running gherkin-lint directly. I noticed the $file path generated always seems to have a / at the beginning, and I'm thinking perhaps that's causing a problem?
If I run the command exactly as it is laid out in the output directly in my terminal, but without that slash at the beginning of the file path, gherkin-lint runs successfully and returns the list of issues:
The text was updated successfully, but these errors were encountered: