Problems with JMS-Metadata-Generator about xsd2php HOT 4 CLOSED

hmm, that is nice
what you can do is to implement a custom naming strategy and find a way to shorten the name

from xsd2php.

thanks for the help :)

I've managed to create a naming strategy, mentioned in this PR:
#49 (comment)

from xsd2php.

to clarify, i had to take another path. the CustomNamingStrategy made problems when trying to (de)serialize, i wasn't able to create the php-object or a schema-valid xml file.

i had to change the generation part:
Created my own JMSWriter to create (sub)folders like in the generation of the php-files and add him to the config.yml

i had to change the (de)serializaion part -> jms-serializer:
created my own FileLocator and set him through:

 $serializerBuilder->setMetadataDriverFactory(new CallbackDriverFactory(function ($metadataDirs, Reader $reader) {
            return new DriverChain([
                new YamlDriver(new MyOwnFileLocator($metadataDirs), new SerializedNameAnnotationStrategy(new CamelCaseNamingStrategy())),
                new AnnotationDriver($reader, new SerializedNameAnnotationStrategy(new CamelCaseNamingStrategy())),
            ]);
        }));

atm it looks like all tests are green :)

from xsd2php.

nice idea...

having such MyOwnFileLocator in the jms/serializer would be nice

from xsd2php.