cucumber / cucumber/pretty-formatter
Missing top level tags
- Dominant language
- Java
- Stars
- 4
- Forks
- 0
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 4
Description
### 👓 What did you see?
With v2, top level tags are missing. "Current" behavior, ie. with @cucumber/cucumber@12.1.0, before the https://github.com/cucumber/cucumber-js/pull/2629, ie. with the most recent message-based implementation:
```
$ cucumber-js
Feature: a feature
@foo
Example: an example # features/foo.feature:6
✔ Given a step # features/definitions.js:3
```
### ✅ What did you expect to see?
Expect to see `@foo\nFeature: [..]`, as shown below, using non-message based implementation.
```
$ cucumber-js
@foo
Feature: a feature # features/foo.feature:2
foobar
@foo
Example: an example # features/foo.feature:6
Given a step
1 scenario (1 passed)
1 step (1 passed)
0m00.004s (executing steps: 0m00.000s)
```
### 📦 Which tool/library version are you using?
node v20.19.4
@cucumber/cucumber v12.1.0
### 🔬 How could we reproduce it?
Simple repository to run & view everything mentioned above: https://github.com/badeball/reproducible-issues/tree/master/cucumber/pretty-regressions
### 📚 Any additional context?
_No response_
Contributor guide
Research direction
Start with the reproducible case in reproducible-issues/cucumber/pretty-regressions and compare its current output with the expected output in this issue. Done means the top-level @foo tag appears before the Feature line while the nested tag and remaining report output still render correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, javascript
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100