Closed renatogcarvalho closed 3 years ago
To circumvent this issue my temporary solution was (I hope until we can get this fixed) set "exclude-from-classmap" in Composer.json: https://getcomposer.org/doc/04-schema.md#exclude-files-from-classmaps
"autoload": {
"psr-4": {
"": "src/"
},
"classmap": [
"app/AppKernel.php",
"app/AppCache.php"
],
"exclude-from-classmap": [
"vendor/steevanb/doctrine-read-only-hydrator/ComposerOverloadClass/Hydrator/ReadOnlyHydrator.php",
"vendor/steevanb/doctrine-read-only-hydrator/ComposerOverloadClass/Hydrator/SimpleObjectHydrator.php"
]
}
Hello folks,
Any ideas here? Is the "exclude-from-classmap" route the only way to circumvent this issue?
+1 Happens only with me on different environments than prod and dev
I think you have a misstake in your configuration.
DoctrineReadOnlyHydrator could be used with ComposerOverloadClass, to show detailed times in Symfony WebProfiler.
But in prod env, you should not use ComposerOverloadClass with DoctrineReadOnlyHydrator, as it's not usefull.
Could you please show me your composer.json ?
https://github.com/steevanb/doctrine-read-only-hydrator/pull/18 should fix the problem as well
On a Symfony project, running "composer install -o" gives the error below:
To circumvent this issue I have to run:
However, none of the commands work after this even though the application was installed:
Any ideas on how I can get this fixed?
Best Regards,
Renato.