The next gherkin release will add an optional GherkinCompatibilityMode feature flag to the Parser. See Behat/Gherkin#349

This is because the legacy / default behaviour parses feature files in a way that has some edge cases / small details that differ from the official cucumber/gherkin parsers. The new compatibility mode option allows consumers to opt-in to parser behaviour that matches the official parsers.

Once that is released, we will want to expose it as a new configuration option in Behat.

We will also need to update Behat functionality (particularly the Pretty formatter) that depended on the legacy parsing.

• Document the option and the differences in behaviour (for end users and extension authors)