Ciaran McNulty
Ciaran McNulty
Hi, I wanted to draw your attention to [cucumber/gherkin](https://github.com/cucumber/gherkin-php), which I recently built within the cucumber org The plan is to eventually replace behat/gherkin in Behat with this parser. Probably...
I think we should enumerate the common extension points in behat, which I suspect are: 1. Register a Formatter 2. Do something else while listening to hooks 3. Provide objects...
This incorporates the compatibility layer from https://github.com/Behat/Gherkin/pull/253 into Behat, as a configuration file flag ```yml default: gherkin: parser: cucumber ``` The expectation is that at some point in the future...
This is something that is implemented in e.g. the symfony extension, but we could do it in core Rather than instantiate a Context we should ask the registered (PSR) containers...
We should have a gh workflow that tries to merge `master` into the `4.x` branch
The changelog is currently in a mix of formats, and releasing is pretty manual I quite like the https://github.com/laminas/automatic-releases idea, here's an example of a project workflow https://github.com/scoutapp/scout-apm-php-ext/blob/1.9.x/.github/workflows/release-on-milestone-closed-triggering-release-event.yml
There's been a little discussion in Cucumber around the idea of exposing actions within steps to formatters. An idea for this in PHP would be to expose a Logger of...
There's been a few things merged, can we release 2.3? I'd be happy to if @everzet and @stof are too busy
Currently I'm using a 2-layer approach: * Injecting symfony services to the context with fake infrastructure * Doing end-to-end tests with symfony driver and real infrastructure It's currently not possible...
Currently the `file` of a test is sourced from reflection around the classname (e.g. https://github.com/sebastianbergmann/phpunit/blob/081c27a7dea2c4dd48d624c4961b2cea060cbced/src/Event/Value/Test/TestMethod.php#L200) It'd be good to be able to configure some sort of prefix, to be able...