Describe the bug
In the cucumber docs, see alternate text
It allows using word1/word2 to make a loose match, much like you can add (s) to match with s or not s at the end.
I tried using it, Then I check/enable the {string} checkbox/toggle - since for us, "toggle" and "checkbox" are interchangeable and the code behind them is the same.
The editor does not recognize that and it shows a little squiggly line showing it is not defined. But it runs just fine.
To Reproduce
Steps to reproduce the behavior:
Add a step like Then('Then I check/enable the {string} checkbox/toggle', ...)
In a feature file, try using Then I enable the "Foo Bar" toggle
See that in the editor, it shows the step is not defined, and CMD+click does not work. However just running cucumber works so you know it is valid or it would complain.
Expected behavior
It recognizes the Then I enable the "Foo Bar" toggle and cmd+click on it takes you to the step definition for Then('I check/enable the {string} checkbox/toggle')
Screenshots
If applicable, add screenshots to help explain your problem.
Describe the bug In the cucumber docs, see alternate text
It allows using
word1/word2
to make a loose match, much like you can add(s)
to match with s or not s at the end.I tried using it,
Then I check/enable the {string} checkbox/toggle
- since for us, "toggle" and "checkbox" are interchangeable and the code behind them is the same.The editor does not recognize that and it shows a little squiggly line showing it is not defined. But it runs just fine.
To Reproduce Steps to reproduce the behavior:
Then('Then I check/enable the {string} checkbox/toggle', ...)
Then I enable the "Foo Bar" toggle
Expected behavior It recognizes the
Then I enable the "Foo Bar" toggle
and cmd+click on it takes you to the step definition forThen('I check/enable the {string} checkbox/toggle')
Screenshots If applicable, add screenshots to help explain your problem.
Cucumberautocomplete part of VSCode settings: