Something strange happened to me today : a collegue changed something in config/app.php , so that a different class is used as a service provider instead of the original one.
The code for this new class is in a package that was added to composer.json.
I updated from SVN and got both new files, but then composer update didn't work, because this somehow uses the config/app.php , which was broken, because it didn't know the class, which of course would only be in vendor AFTER composer update !
So my question is : why would composer update need anything that is in config/app.php ? And how to prevent something like this in the future?
via Chebli Mohamed
Aucun commentaire:
Enregistrer un commentaire