-
Notifications
You must be signed in to change notification settings - Fork 149
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 built-in cucumber expressions #285
support built-in cucumber expressions #285
Conversation
We have a similar problem, can this be merged or is there anything left? |
@johny2000uwb Can this be merged or is there anything let to be done? I can verify that this fixes the issue at least for my test cases. |
I can also verify that this fixes #286 (invalid regexp makes the parser crash) |
Hi @qvdk, Thanks for your making your first contribution to Cucumber, and welcome to the Cucumber committers team! You can now push directly to this repo and all other repos under the cucumber organization! 🍾 In return for this generous offer we hope you will:
On behalf of the Cucumber core team, |
Hi @aslakhellesoy Thanks for the invitation ! |
I really need this, is there a build available with this fix? Or when is next release scheduled? never mind! I just saw the instructions to build from source. I'll just go ahead and do just that |
Add the support of built-in cucumber expressions.
Previously, this type of expression crash the gherkin editor as described into #278 and #267
Limitation: custom cucumber expressions are not detected.
This path fixes also the issue #286.
When using a pattern like
@Given("^(?>region|regions) of type (.*) (?>are|is) covering all references$")
, theStepMatcher
convert it as a malformed pattern^(<p>|?>region|regions) of type (.*) (?>are|is) covering all references$
.More, it causes an exception with the side effect that the F3 key stop to work.