⚙️ Configuration
Gherkin PowerTools works out-of-the-box, but you can tailor it to your team's style guide via your settings.json.
Available Settings
| Setting | Default | Description |
|---|---|---|
gherkinPowerTools.indentation.steps |
4 |
Number of spaces to indent all steps (Given, When, Then, And, But). |
gherkinPowerTools.tables.alignToKeyword |
true |
If enabled, tables dynamically pad their left border to match the text length of the preceding step. |
gherkinPowerTools.emptyLines.betweenScenarios |
1 |
Enforces the exact number of blank lines between Scenario and Rule blocks. |
gherkinPowerTools.tags.format |
"wrap" |
Choose "wrap" to split long tags across lines, or "singleLine" to keep them contiguous. |
Example Configuration
{
"gherkinPowerTools.indentation.steps": 2,
"gherkinPowerTools.tables.alignToKeyword": true,
"gherkinPowerTools.emptyLines.betweenScenarios": 1,
"gherkinPowerTools.tags.format": "wrap"
}
Workspace vs User Settings
- User Settings: Apply globally to all your projects.
- Workspace Settings: Apply only to the current project (via
.vscode/settings.json).
Team Standardization
For team projects, commit a .vscode/settings.json with your preferred Gherkin PowerTools settings so all contributors use the same formatting rules.