Scenario Outline - changes to steps not recognised unless you comment out the Examples/Scenarios table

[monsoon53]

👓 What did you see?

For tests that have Scenario Outline with Examples/Scenarios table - changes to steps are not recognised unless you comment out the Examples/Scenarios table.

✅ What did you expect to see?

If an existing step is amended or a new step is added, I would expect it to be recognised as a new step and given the option to define the step in a steps class.

📦 Which tool/library version are you using?

Cucumber for VSCode 1.10.0 Reqnroll.xUnit 2.2.1

🔬 How could we reproduce it?

Create a test with Scenario Outline and Examples/Scenarios table - make a change to a step, or add a new step. Observe that the step is not recognised as being new, and needing to be defined - until you comment out the Examples/Scenarios table, will then be recognised as being new and give you the option to define the step.

📚 Any additional context?

No response

[Ndus3-Martin]

I've the same issue. Using the same version of cucumber extension but without Reqnroll. My guess it is a bug or something is not configured properly as one of the closed/solved bugs refers to this back in 2023/2024: https://github.com/cucumber/language-service/issues/149

Without the comment

With the comment

[kieran-ryan]

@monsoon53, @Ndus3-Martin thanks for raising! Possible to share a minimum reproducible example with a feature file and associated step definitions?