Open jonyo opened 5 months ago
I was able to reproduce the issue as mentioned by @jonyo in my case steps definition used with parsers.parse is not identified, other step definition used without parsers.parse are able to get the step definition by CucumberAutoComplete However the script works when executed, issue is only with CucumberAutoComplete
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: