Why falling on the Composer reset the cache of Symfony?

Question

Why falling on the Composer reset the cache of Symfony?

Good evening, all with a holiday :)

There is a Symfony 2.3 with a bunch of other packages. All this is managed by Composer.
Worked it myself and did not have any problems.

Then I manually ran a dump with a key "-o"

composer dumpautoload -o

Now every time you update (composer update), and no matter what the package (or even all) of it falls on you reset the cache in Symfony2.3, because can't find the class. Even though the file and class exist of course.

If you then manually run

composer dumpautoload -o
app/console cache:clear
.....

Then everything is fine.

But he runs without the flag "-o", and thus every time it lands.

What am I doing wrong, and how to get it?) I hope, clearly explained...

Ahmad38 asked October 3rd 19 at 03:57

More answers about "Why falling on the Composer reset the cache of Symfony?"

1 answer

hattie.Johnston80 answered on · Answer 1 · 2019-10-03T03:59:56.311Z

hattie.Johnston80 answered on October 3rd 19 at 03:59

when you forgive composer to generate an optimized autoloader, it generates HashMap all classes then that would not check out the file or not, to search for directories etc. So in theory when you do composer update does not update this HashMap. Since then he works with-o flag. The idea is to re-invoke the command dumpautoload without the option `o` needs to solve the problem.

It doesn't. I understand the problem, but I do not understand how to solve it.
You can try to carry all the folder /vendor and put again, I think will help? - Ahmad38 commented on October 3rd 19 at 04:02