-
Notifications
You must be signed in to change notification settings - Fork 92
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
Migrate parser to cucumber/common
?
#245
Comments
This will probably require a major version bump in Behat (the PyStringNode and the TableNode are accessed directly in steps, and other nodes can be accessed in hooks). However, if the quality of the PHP code maintained by the Cucumber team can be good, I'm in favor of it. |
and we could indeed have an intermediate step where |
Yeah it would basically be the same mapping as NdJsoNLoader does in the tests, except from cucumber objects instead of JSON |
It requires to implement parser generator for gasparnagy/berp first (template file). |
@unkind Just to update, I've started work on this and have a cucumber/messages implementation published on packagist I've implemented the gherkin berp stuff, just need to make the various other objects that the parser uses (mostly copying the Java implementation) |
How it's going? Need some help? |
Not sure about English language, but "Scenario" instead of "Example" in Russian sounds literally like "Script" for a movie or even a theatrical play. It's harder to represent to a newbies. |
See #253 |
I'm going to do a spike at porting the cucumber parser over to PHP within the cucumber repository. This would contain a complete AST of value objects we could use.
For BC it should be possible to write a thin translation layer to map that to the existing Gherkin objects in this repo via a Loader, but a future version of Behat could rely on its AST directly, or even at some point rely on its 'pickles'.
Pros:
Cons:
Any thoughts/feedback?
The text was updated successfully, but these errors were encountered: