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
I searched existing and closed issue and couldn't find any information on my small problem. If seen in the UPGRADING file, that the name key inside jms_serializer.metadata.directories must be provided.
Thing is, we never specified any directories. Our config looks like this (and worked fine, only using auto detection):
PHP Fatal error: Uncaught exception 'Symfony\Component\Config\Definition\Exception\InvalidConfigurationException' with message 'The attribute "name" must be set for path "jms_serializer.metadata.directories".' in /src/git/graviton2/vendor/symfony/symfony/src/Symfony/Component/Config/Definition/PrototypedArrayNode.php:244
Stack trace:
#0 /src/git/graviton2/vendor/symfony/symfony/src/Symfony/Component/Config/Definition/BaseNode.php(264): Symfony\Component\Config\Definition\PrototypedArrayNode->normalizeValue(Array)
So i guess the question is: Do we really need to specify some directories? What do I define if I don't have anything to specify? ;-)
Thanks for a short clarification
And thanks for your great work!
The text was updated successfully, but these errors were encountered:
@goetas aah... i've found a bundle that defines a directory in its config.yml.. ok, thx.. closing the issue.. sorry for the premature issue creation ;-)
Hi guys..
I searched existing and closed issue and couldn't find any information on my small problem. If seen in the
UPGRADING
file, that thename
key insidejms_serializer.metadata.directories
must be provided.Thing is, we never specified any directories. Our config looks like this (and worked fine, only using auto detection):
So after updating the Bundle to 2.0.0, we get
So i guess the question is: Do we really need to specify some directories? What do I define if I don't have anything to specify? ;-)
Thanks for a short clarification
And thanks for your great work!
The text was updated successfully, but these errors were encountered: