This PR was merged into the 2.1-dev branch.
Discussion
----------
Related to https://github.com/Sylius/Sylius/pull/11029. Damn, this was really hard to fix.
Commits
-------
9609cc1171 Fix a weird bug causing failures in Sylius
This PR was merged into the 2.1-dev branch.
Discussion
----------
Fixes#86, fixes#110.
TODO:
- [x] Documentation
Commits
-------
776af6cc38 Describe accessing driver's service container
b05304858c Introduce a service in the test application that exposes driver's service container
e94285dc0b Fix coding standard
This PR was merged into the 2.1-dev branch.
Discussion
----------
Commits
-------
3f02ad3b58 Mention friends-of-behat forks of Mink-related repositories in the docs
This PR was merged into the 2.1-dev branch.
Discussion
----------
If you need Symfony 3.4 support, I'd recommend using `v2.0.*` releases, supporting two major Symfony versions is enough maintenance work 🎉
Commits
-------
fcf957dc5a Remove support for Symfony 3.4
This PR was merged into the 2.1-dev branch.
Discussion
----------
Commits
-------
e37704744c Add safety check for SymfonyDriverFactory to make sure BrowserKitDriver is installed
f08d450cdf Document "behat.driver.service_container" service
This PR was merged into the 2.1-dev branch.
Discussion
----------
Waiting for Behat to support Symfony 5.
Commits
-------
fbe3fb6c5e Add support for Symfony 4.4 and 5.0; remove for 4.2 and 4.3
This PR was merged into the 2.0 branch.
Discussion
----------
With definition, that has been used instead of reference, container has used to created 2 instances of initializer: one with service id, and one "anonymous", described by spl_object_hash in a container, it broke stateful initializers: in my case initializer was also used to reset state before next scenario/example, and initializing and resetting happened with different instances of initializer.
If the fix and test are OK, let me know if you want me to cherry-pick the fix onto master and created additional pull request for master.
Commits
-------
06104478cc Fix referencing context initializers
With definition, that has been used instead of reference, container has
used to created 2 instances of initializer: one with service id, and one
"anonymous", described by spl_object_hash in a container, it breaked
stateful initializers: in my case initializer was also used to reset
state before next scenario/example, and initializing and resetting happened
with different instances of initializer
