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
...to find the specified structure across the opened workspace and associate .feature files with corresponding matchers? Users currently have to tune their local workspace settings:
// in a local .vscode/settings.json{"cucumber.glue": ["path/to/dir/tests/**/*.ext"]}
... so that extension can find the matchers.
π¦ Which tool/library version are you using?
Name: Cucumber
Id: CucumberOpen.cucumber-official
Description: Cucumber for Visual Studio Code
Version: 1.5.1
Publisher: Cucumber
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=CucumberOpen.cucumber-official
π¬ How could we reproduce it?
Move the tests/features/ dir (and possibly re-configure your build system for this change) in some nested dir, not in the top-level dir, observe the Undefined step and no goto definition in the editor for every step in the .features files. Default VScode settings.
Are you suggesting we add ./**/ to the beginning of every cucumber.glue glob? While it might fix your problem without having to change any settings, it might also slow down the scanning if there are many files in your workspace. It's primarily limited by how fast the globbing library works, which I haven't benchmarked.
Starting glob patterns with **/ is about 10x times slower (0.074s -> 0.732s) for synchronous operations and 16x times slower (0.067s -> 1.101s) running asynchronously.
This benchmark suite contains significantly more files than would be contained within a typical Cucumber environment repository, so would not be as drastic in practice. Although it should be possible to support this request, we would first need to optimise existing performance (#152) - particularly how we watch and read files; allowing us to offset the slower globbing and provide a better out-of-the-box experience.
π What did you see?
When I open a workspace that has
tests/features/*
structure somewhere in it, every step is marked asUndefined
.β What did you expect to see?
Should the extension use the settings...
...to find the specified structure across the opened workspace and associate
.feature
files with corresponding matchers? Users currently have to tune their local workspace settings:... so that extension can find the matchers.
π¦ Which tool/library version are you using?
π¬ How could we reproduce it?
Move the
tests/features/
dir (and possibly re-configure your build system for this change) in some nested dir, not in the top-level dir, observe theUndefined step
and nogoto definition
in the editor for every step in the.feature
s files. Default VScode settings.MRE: https://github.com/zohnannor/cucumber-vscode-mre/tree/workspace
This text was originally generated from a template, then edited by hand. You can modify the template here.
The text was updated successfully, but these errors were encountered: