cucumber / cucumber/vscode

.feature editing without glue

Open Beginner friendly
#344 0 comments 1 reaction 0 assignees View on GitHub
Dominant language
TypeScript
Stars
88
Forks
33
PR merge metrics
No merged PRs in 30d

Description

### 🤔 What's the problem you're trying to solve?

We entirely use Gherkin in early stages of design to agree on features and properly define them. The yellow underlines under every step are quite grating, and gives a bad impression to non-technical stakeholders when projected for the whole room to see.

### ✨ What's your proposed solution?

A `.vscode/settings.json` setting to make glue opt in.

### ⛏ Have you considered any alternatives or workarounds?

_No response_

### 📚 Any additional context?

_No response_

Contributor guide

Open the contributing guide

Research direction

Start with the extension's settings handling and the proposed .vscode/settings.json entry, then trace how glue-related step diagnostics are enabled. Done means Gherkin files no longer show yellow underlines by default, while the new setting can opt glue checking back in.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vscode
Domain
developer-experience, tooling
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.