Erik Huelsmann
Erik Huelsmann
@aslakhellesoy isn't this solved with the #1741 merge?
I just checked the site (but not any security reports); the information that I need as a maintainer isn't there in a way that it allows me to find it...
I would argue that the reverse is true: if we part with our own parser (and use theirs), we can use more of their tooling. My proposal is to move...
I've tried fixing their parser and succeeded. However, quite soon after the working code was contributed, they broke it again. In order to fix the official parser, I'll need to...
The Perl code in their parser has been upgraded to comply with the latest language definition. Waiting for a release.
Current state of affairs is that there is no dependency on proto if anymore. Instead, there are jsonschemas which map to ndjson structures. Which allows tapping into the wire protocol...
Oh. And the Perl parser has been released.
To anybody reading this issue: I've not been ignoring this response. Instead, @cobber and I have been exchanging e-mails on how to get support into a next release.
The Gherkin release notes suggest that in Gherkin 6 `Scenario Outline` vs `Scenario` has been resolved: https://github.com/cucumber/cucumber/blob/master/gherkin/CHANGELOG.md#6013---2018-09-25
After cucumber/cucumber#694 gets merged the Gherkin parser has everything we need to drive cucumber tests: the generated `pickles` list all the scenarios and their steps that will be executed. This...