-
-
Notifications
You must be signed in to change notification settings - Fork 216
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does not use custom TypedFieldMapper #557
Comments
I found that |
Hmm, I think maybe this is not related to migrations at all. I checked Here, I have on top: $a->setTypedFieldMapper(new \App\ORM\TypedFieldMapper\MyTypedFieldMapper());
$a->setEntityNamespaces(['App' => 'App\\Entity']); and then few lines below it $a->setTypedFieldMapper(new \Doctrine\ORM\Mapping\DefaultTypedFieldMapper()); So, the issue is that my Any ideas how to fix this please? |
Ok, so I guess this has to be implemented: doctrine/DoctrineBundle#1696 I will close this issue, as it is unrelated to migrations, but please, anybody knows how I can call
AFTER all the default ones are called? |
As of doctrine/DoctrineBundle#1802 we have a way to specify any service as This is documented at https://symfony.com/bundles/DoctrineBundle/2.13.x/configuration.html |
I have an issue with migrations, as they do not use my custom
TypedFieldMapper
.I configure it like this in services.yaml:
And this works fine when running the app. But when doing
doctrine:migrations:diff
then this is not used and insteadDoctrine\ORM\Mapping\DefaultTypedFieldMapper
is used.How do I tell migration bundle to use my custom typed field mapper?
The text was updated successfully, but these errors were encountered: