Christophe Coevoet

@barryswaisland-eagleeye sure there's much more in BDD. But those "more" things are not solved by software (and so would not be solved more by Behat than by Cucumber, otherwise Cucumber...

Btw, regarding https://github.com/sass/sass/issues/3171, this feature might even be useful as it means that those private members can be configured but cannot be written later.

Those tests would then be cases for which we create a cucumber-parity issue in the issue tracker (if we don't have it yet), and they will eventually be gone. but...

Note that this might help (a bit) cucumber regarding https://github.com/cucumber/gherkin/issues/53 (the low number of tests for bad input probably contributes to the low code coverage situation as it means error...

Note that another option could be to switch to phpstan, which is more actively maintained these days (and is already used as static analyzer for the tag-expressions PHP implementation). This...

#229 solved those cases of failures in `preg_replace` by casting the `null` value to an empty string instead of properly throwing an exception (which means it would produce corrupted parsing...

Thanks for this answer.

This should probably be documented in the Gherkin reference page at https://cucumber.io/docs/gherkin/reference. This is the page documenting the Gherkin language. Regarding the UTF-8 BOM, the java parsers allows using it...

I opened [a separate issue](https://github.com/cucumber/gherkin/issues/516) to discuss the topic of the BOM, to keep things focused.

The best way to solve this parity issue is probably to attempt fixing the issue in cucumber before we migrate instead of adding the parse error in our implementation.