-
Notifications
You must be signed in to change notification settings - Fork 222
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
Default parser switched to cfparse #472
Default parser switched to cfparse #472
Conversation
Codecov Report
@@ Coverage Diff @@
## master #472 +/- ##
==========================================
+ Coverage 95.91% 96.30% +0.38%
==========================================
Files 49 49
Lines 1640 1839 +199
Branches 179 195 +16
==========================================
+ Hits 1573 1771 +198
- Misses 41 43 +2
+ Partials 26 25 -1
Continue to review full report at Codecov.
|
Have to be merged after #469 because it brokes obsolete test case |
8ce5dbb
to
749190c
Compare
749190c
to
52b58f8
Compare
7aa9698
to
c4b8da7
Compare
In most cases, cfparse parser is more useful than a string parser. It could be used almost everywhere, just one edge-case is when the step definition contains "{....}" pair. In this case user still could select string parser