The features and glue settings in the language server are only configurable in the configuration sent during the startup process. However, almost all clients only support sending them in the global settings. This forces users to declare all possible styles to ensure that features and glue work as expected. Additionally, this can reduce performance when the search pattern is extensive, and conflicts may arise in the groups at times.
✨ What's your proposed solution?
Provide a way to set configurations at the workspace level. We can reuse the cucumber.json settings file from cucumber.js.
⛏ Have you considered any alternatives or workarounds?
Alternatively, we can add a configuration file like cucumber-config.json, inspired by jsconfig.json of TypeScript, which does nothing except providing IDE support.
Great shout @binhtran432k! This aligns with other requests where Cucumber configuration files are supported by tools but not the Language Server implementation (cucumber/vscode#151) 👍
🤔 What's the problem you're trying to solve?
The
features
andglue
settings in the language server are only configurable in the configuration sent during the startup process. However, almost all clients only support sending them in the global settings. This forces users to declare all possible styles to ensure thatfeatures
andglue
work as expected. Additionally, this can reduce performance when the search pattern is extensive, and conflicts may arise in the groups at times.✨ What's your proposed solution?
Provide a way to set configurations at the workspace level. We can reuse the
cucumber.json
settings file fromcucumber.js
.⛏ Have you considered any alternatives or workarounds?
Alternatively, we can add a configuration file like
cucumber-config.json
, inspired byjsconfig.json
of TypeScript, which does nothing except providing IDE support.📚 Any additional context?
None
This text was originally generated from a template, then edited by hand. You can modify the template here.