UnderTest.FeatureLint.VsCode issueshttps://gitlab.com/under-test/undertest.featurelint.vscode/-/issues2021-11-05T16:48:28Zhttps://gitlab.com/under-test/undertest.featurelint.vscode/-/issues/51NPM install fails due old version of vscode2021-11-05T16:48:28Zm tNPM install fails due old version of vscodeNPM install fails due old version of vscode
![imagen](/uploads/7203b8ad79aed2252fac22b191f887a9/imagen.png)
This issue is fixed updating vscode dependency from 1.1.33 to 1.1.37NPM install fails due old version of vscode
![imagen](/uploads/7203b8ad79aed2252fac22b191f887a9/imagen.png)
This issue is fixed updating vscode dependency from 1.1.33 to 1.1.37https://gitlab.com/under-test/undertest.featurelint.vscode/-/issues/44Add gutter updates for all non-empty lines2020-08-12T02:28:31ZRon MyersAdd gutter updates for all non-empty linesThis should be able to be turned off with a setting.This should be able to be turned off with a setting.release-v0.1.0Ron MyersRon Myershttps://gitlab.com/under-test/undertest.featurelint.vscode/-/issues/43Improve README2020-08-06T03:33:38ZRon MyersImprove READMECurrently it is a bit out of date.Currently it is a bit out of date.release-v0.1.0Ron MyersRon Myershttps://gitlab.com/under-test/undertest.featurelint.vscode/-/issues/37Have the extension look for a local tool before a global tool2020-07-08T00:47:09ZchrisdmacraeHave the extension look for a local tool before a global tool```
Feature: resolve undertest.featurelint for parsing
Teams that are dotnet specific likely have no trouble installing a global tool, and will resolve it accordingly.
As a team using undertest.featurelint, they may have projects or te...```
Feature: resolve undertest.featurelint for parsing
Teams that are dotnet specific likely have no trouble installing a global tool, and will resolve it accordingly.
As a team using undertest.featurelint, they may have projects or teams that are not primarily dotnet and don't have the tooling installed, or have a reason to use multiple versions of UnderTest.FeatureLint, so would need project specific versions of the tool or an embedded version.
Scenario: extension resolves local tool
Given that UnderTest.FeatureLint is installed as a local tool
And that UnderTest.FeatureLint is installed as a global tool
When when the extension attempts to resolve feature lint
Then the extension resolves the local tool
Scenario: extension resolves global tool
Given that UnderTest.FeatureLint is not installed as a local tool
And that UnderTest.FeatureLint is installed as a global tool
When when the extension attempts to resolve feature lint
Then the extension resolves the global tool
Scenario: extension resolves embedded tool
Given that UnderTest.FeatureLint is not installed as a local tool
And that UnderTest.FeatureLint is not installed as a global tool
When when the extension attempts to resolve feature lint
Then the extension resolves an embedded version of the tool,
And emits an error that informs the user that a local or global version should be installed.
```release-v0.1.0Ron MyersRon Myershttps://gitlab.com/under-test/undertest.featurelint.vscode/-/issues/34After installing requirements ENOENT error until restart2020-08-08T13:40:35ZKais Ben SalahAfter installing requirements ENOENT error until restartHello,
I installed the extension along with the required featurelint tool. Unfortunately, the extension always fails with an ENOENT error whenever it starts loading.
This is what the error message says:
> Cannot featurelint the gherki...Hello,
I installed the extension along with the required featurelint tool. Unfortunately, the extension always fails with an ENOENT error whenever it starts loading.
This is what the error message says:
> Cannot featurelint the gherkin file with error: spawn featurelint ENOENT
I'm pretty sure that the tool is correctly installed, because this what I get when checking the version:
> featurelint --version
> UnderTest.FeatureLint 0.4.2
I can provide more information, as required.https://gitlab.com/under-test/undertest.featurelint.vscode/-/issues/32Improve step autocomplete2020-05-03T11:03:32ZEvan CahillImprove step autocompleteThe autocomplete of Gherkin steps we're currently using looks at the current workspace (configurable to include additional external libraries/directories) and pulls **all** steps for its suggestions.
Sample existing Gherkin:
```gherkin...The autocomplete of Gherkin steps we're currently using looks at the current workspace (configurable to include additional external libraries/directories) and pulls **all** steps for its suggestions.
Sample existing Gherkin:
```gherkin
Feature: A sample of Gherkin
Scenario Outline: Gherkin autocomplete finds steps to suggest
Given there exists Gherkin steps
When a '<step>' keyword is typed
Then step suggestions appear
Examples: Step keywords
| step |
| Given |
| When |
| Then |
```
In the current functionality regardless of what keyword was typed all three of the above steps are suggested. Proposed improvement is to scope the suggested autocomplete by keyword, potentially providing a configuration to toggle keyword scoping.
```gherkin
Feature: Gherkin autocomplete
Scenario: Existing Gherkin steps
Given this is a 'Given' step
When this is a 'When' step
Then this is a 'Then' step
Scenario Outline: Gherkin autocomplete finds steps to suggest scoped by keyword
Given there exists Gherkin steps
When a '<step>' keyword is typed
Then step suggestion '<suggestion>' appears
Examples: Step keywords
| step | suggestion |
| Given | this is a 'Given' step |
| When | this is a 'When' step |
| Then | this is a 'Then' step |
```release-v0.1.0Ron MyersRon Myershttps://gitlab.com/under-test/undertest.featurelint.vscode/-/issues/29Add support to add BadPhrases to the local config2019-11-04T23:12:45ZRon MyersAdd support to add BadPhrases to the local configrelease-v0.1.0Ron MyersRon Myershttps://gitlab.com/under-test/undertest.featurelint.vscode/-/issues/28Add support for adding to configuration list when hitting specific rules2019-11-04T23:12:45ZRon MyersAdd support for adding to configuration list when hitting specific rulesInitially, we can add:
* [ ] BadPhrases #29
* [ ] WhiteListed upper case words #30 Initially, we can add:
* [ ] BadPhrases #29
* [ ] WhiteListed upper case words #30 release-v0.1.0https://gitlab.com/under-test/undertest.featurelint.vscode/-/issues/27Update the README to point to the FeatureLint docs2019-11-02T16:40:29ZRon MyersUpdate the README to point to the FeatureLint docsAs we have configuration now. We should point there.As we have configuration now. We should point there.release-v0.1.0Ron MyersRon Myershttps://gitlab.com/under-test/undertest.featurelint.vscode/-/issues/13Add support for configuration2019-11-02T16:41:34ZEvan CahillAdd support for configurationInitially a `gherkinlinter.enable` (or similar) flag to enable/disable linting would satisfy this feature request.
This could then lead into allowing users to set other values (once corresponding functionality is implemented) like:
- `...Initially a `gherkinlinter.enable` (or similar) flag to enable/disable linting would satisfy this feature request.
This could then lead into allowing users to set other values (once corresponding functionality is implemented) like:
- `workingDirectories`: indicate what folders/directories to include when linting
- `runType`: option to have the linter run `onSave` (default, current behavior) or `onType`
- `autoFix`: enable/disable (disabled by default) auto fixing of errors
- `rules`: include custom linting rules, with support for something like `"gherkinlinter.rules": { "config": "C:\mydirectory\gherkin-rules.json" }` to specify a file to load in (could be cross-compatible with how we plan to allow custom rules configuration in `FeatureLint` proper)release-v0.1.0https://gitlab.com/under-test/undertest.featurelint.vscode/-/issues/12Add support for multiple file checks2019-11-02T16:41:42ZRon MyersAdd support for multiple file checksCurrently, we only used single file checks.
Add support for folder based checks.Currently, we only used single file checks.
Add support for folder based checks.release-v0.1.0