You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is very impractical in some situations. We have several composer.json files in our project:
tools/.phpunit/composer.json (PHPUnit)
composer.json (actual project)
We do this because there are conflicts between PHPUnit and other tools (like Psalm) for their respective dependencies.
We had to add this library here to the main composer.json because it has Symfony dependencies and we would have duplicate Symfony packages otherwise.
Due to this dependency, a PHPUnit is now installed in the main project, which causes conflicts.
I would assume that the explicit dependency in require is not needed, since you will certainly not use this library without PHPUnit and it is therefore always present.
The text was updated successfully, but these errors were encountered:
add support for phpunit 11 (#79) · SymfonyTest/SymfonyConfigTest@59f4d3b · GitHub added
"require": "phpunit/phpunit
to thecomposer.json
.This is very impractical in some situations. We have several composer.json files in our project:
tools/.phpunit/composer.json
(PHPUnit)composer.json
(actual project)We do this because there are conflicts between PHPUnit and other tools (like Psalm) for their respective dependencies.
We had to add this library here to the main composer.json because it has Symfony dependencies and we would have duplicate Symfony packages otherwise.
Due to this dependency, a PHPUnit is now installed in the main project, which causes conflicts.
I would assume that the explicit dependency in
require
is not needed, since you will certainly not use this library without PHPUnit and it is therefore always present.The text was updated successfully, but these errors were encountered: