-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support steps defined with strings instead of regexes #35
Comments
Looks like new format should be supported without any code changes. Do you have any unsupported cases examples ? |
@alexkrechik will post a sample |
@alexkrechik I've just made the simplest possible cucumber-js sample and there I get the squiggly lines: And no autocomplete: |
Looks like, steps definitions first argument should be regexp's (https://github.com/cucumber/cucumber-js/blob/master/CHANGELOG.md#200-rc4-2016-12-19): But, in your app, step definitions first argument type is string: Are you sure, that they are valid? |
@alexkrechik of course they are. you can try it out by installing deps and running The sample is taken from the official documentation here: https://github.com/cucumber/cucumber-js/blob/master/docs/nodejs_example.md |
@alexkrechik so I tried with regexes and you were right-those work just fine. Thanks for your response. I will rename this bug then. |
Will be fixed with #39 in the nearest release. |
Should be fixed in 2.1.0 version of plugin |
steps which are defined with strings are not autocompleted
The text was updated successfully, but these errors were encountered: