Missing feature descriptions

[badeball]

👓 What did you see?

With v2, feature descriptions are no longer printed. "Current" behavior, ie. with @cucumber/cucumber@12.1.0, before the revert, 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 foobar, 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

[davidjgoss]

Now seems like a good time to re-assess this feature - it was in the original community-maintained version that Julien forked a while ago.

In a feature file, any of these things can have a description:

• Feature
• Rule
• Background
• Examples table
• Scenario

The old JS implementation includes just the feature descriptions but no others.

What problem is this solving for users? I'm fine in theory with including descriptions, behind an option, but shouldn't we also include the descriptions of rules? What about backgrounds, examples tables and scenarios (which aren't so easy because we work with pickles at this level)?

[badeball]

What problem is this solving for users? I'm fine in theory with including descriptions, behind an option, but shouldn't we also include the descriptions of rules? What about backgrounds, examples tables and scenarios (which aren't so easy because we work with pickles at this level)?

Tbh, I mostly created this issue and #24 to mention disparities in case they were unintentional, but the issues themselves aren't of particular importance to me. With that said though - I think it's pretty cool when the output mimicks the actual file contents,