-
-
Notifications
You must be signed in to change notification settings - Fork 691
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
Cucumber expressions fix regexp parsing #254
Cucumber expressions fix regexp parsing #254
Conversation
Sorry on the delay on a more in depth review. I trust your writing so if you don't want to wait on me, go ahead. :) |
Hey @jaysonesmith thanks for the heads up. The review request was also meant as a heads up for you to look at the implementation because you started it originally. I'll press on. |
Oh, I've done a brief look at it, but at some point, I'd love to setup up a break point and walk through it step by step to gain a better understanding. 👍 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM (the java stuff is all too foreign for me to comment on.)
Woot!! |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Summary
Fix how regexps are parsed
Details
See #253 for a description of the problem. This is an alternative implementation which leverages the existing regexp parser in
TreeRegexp
, which means consistency and reliability (compared to parsing regexp with regexp).How Has This Been Tested?
Types of changes
Checklist: