-
Notifications
You must be signed in to change notification settings - Fork 230
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
Utilize Doctrine common for mappings #124
Conversation
I cleaned up the tests a bit and we have one failure remaining:
I traced the outstanding calls to
I take it you never added common mapping support to ORM's DoctrineBundle for We don't use the bridge's XmlDriver and YamlDriver classes, and we can probably get away with extending |
indeed, 2.0 does not support the ORM 2.3 (we have other issues too as the mapping drivers are in DoctrineBundle itself in 2.0 whereas they are in the ORM since 2.2) |
@jmikola the need to flip is weird. The ORM does not need to flip the array passed by the DI extensions of the bridge. |
@stof: I looked at the difference between |
ah yeah, indeed. So you may need to re-add the method in the 2.0 branch (forwarding the data to the file locator). |
I came up with an alternate solution, which I'll push in a minute. |
… drivers Since the ODM is using Doctrine Common's mapping drivers for Symfony 2.0, we need to remove the setNamespacePrefixes() method call and instead pass its argument to the driver constructor. See: symfony/symfony@3ca1ccb for some historical context.
seems good to me. If all works now, please merge it so that people stop complaining. And don't forget to remove the extra code when merging into master to avoid useless code :) |
@stof: I didn't think reimplementing |
Utilize Doctrine common for mappings
Ok, merged into |
MongoDB ODM 1.0.0-BETA4 does not include the mapping refactoring introduced in #124.
This replaces #116 and #122.
@stof: Please take a look at my revisions to the test class.
The only question I have is that I had to flip the key/value pairs from the previous tests in order to work with the new locator service. Does this pose a problem for the extension class, or does the bridge take care of the change for us?