Skip to content
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

Outsourcing the Gherkin parsing #94

Open
wants to merge 6 commits into
base: develop
Choose a base branch
from

Conversation

enkessler
Copy link
Contributor

This PR delegates the burden of parsing feature files to the gherkin gem (via the cuke_modeler gem as an abstraction layer).

Benefits:

  • No having to reverse engineer the grammar of Gherkin
  • Will work with non-English dialects of Gherkin
  • Probably other stuff (subjective)

Drawbacks:

  • Some existing rules will need to be changed or replaced (mostly due to the rules in question being related to incorrect Gherkin and the parser will simply explode in such cases)

In any case, because it's a rather significant change, I'm not holding my breath on this PR ever getting accepted. But it's something to think about.

Delegating the parsing of feature files to the 'cuke_modeler' gem
instead of trying to parse them ourselves.
Got most of the tests for comments passing again. Some unsupported
behavior will need rethinking.
Conditionalizing a gem dependency so that the project can be tested
across multiple version of Ruby.
Removing Gemfile.lock from source control so that it can be
rebuilt as needed.
Conditionalizing more gem dependencies so that the project can be
tested across multiple version of Ruby.
@enkessler
Copy link
Contributor Author

#107 should get this passing again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant