After installing symfony/serializer
I recognized that my symfony.lock
file got changed:
diff --git a/symfony.lock b/symfony.lock index ba6e23f..bfc391e 100644 --- a/symfony.lock +++ b/symfony.lock @@ -301,5 +301,8 @@ }, "symfony/asset": { "version": "v3.3.10" + }, + "symfony/serializer": { + "version": "v3.3.13" } }
From what I understand, it was introduced with Symfony Flex, but how does it differ from composer.lock
and why is it needed on top of that?
How Does Flex Work. Symfony Flex is a Composer plugin that modifies the behavior of the require , update , and remove commands. When installing or removing dependencies in a Flex-enabled application, Symfony can perform tasks before and after the execution of Composer tasks.
Using Symfony Flex is optional, even in Symfony 4, where Flex is used by default. However, Flex is so convenient and improves your productivity so much that it's strongly recommended to upgrade your existing applications to it.
It is the proper lock file for Symfony recipes instead of trying to guess via the state of composer.lock
Flex keeps tracks of the recipes it installed in the
symfony.lock
file, which must be committed to your code repository (CVS). https://symfony.com/doc/3.4/setup/flex#how-does-flex-work
It was introduced since Flex 1.0.34
version, originally to solve bugs like this: "Configuring recipes executed twice".
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With