Given that Doctrine will remove support for defining ORM metadata in YAML format (see doctrine/doctrine2#5932), we should probably already remove references to this format.
@xabbuh : Sorry for the unrelated comment, but do you know if there is any related issue or comment explaining why Doctrine will not support anymore defining ORM metadata in YAML format ?
(Appart from https://twitter.com/lcobucci/status/752968139705647104)
@ogizanagi Somewhere I read a comment by @Ocramius that the code for it was too fragile IIRC. Maybe he can give you some more insights.
The change will affect ORM 3.0: do you really want to raise it here already? I don't think that you should worry about it yet.
@Ocramius Will the XML and annotation mapping formats change in 3.0? If not, it imo is a good idea not to advocate to use YAML anymore to ease migrating to Doctrine 3.
Not sure yet.
On 13 Jul 2016 18:51, "Christian Flothmann" [email protected]
wrote:
@Ocramius https://github.com/Ocramius Will the XML and annotation
mapping formats change in 3.0? If not, it imo is a good idea not to
advocate to use YAML anymore to ease migrating to Doctrine 3.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/symfony/symfony-docs/issues/6752#issuecomment-232416595,
or mute the thread
https://github.com/notifications/unsubscribe/AAJakOP2UpyNygk3Rb548-6ly8jRRo-tks5qVRd_gaJpZM4JLh8j
.
@Ocramius Where can I find discussions on the removal of YML in D3?! (The post @ https://github.com/doctrine/doctrine2/pull/5932 has more thumbs down than thumbs up at this point...)
@robfrawley we are currently working on rewriting the entire metadata-related internals of the ORM, and the Yaml driver was just long-due removal. We just needed to finally have a practical excuse (3.x + refactoring) to do so, and we did.
The Yaml driver has always been lagging back (bugs, support, docs, etc) due to the squishy format of it (no type checking, no static analysis, no autocompletion), so you'll likely see it implemented by third parties than by Doctrine itself in 3.x.
@Ocramius Thanks for the detailed response. Makes sense; still sad from an end-user perspective but I understand the development need to remove areas that pose difficulties where the return is far less than the investment. Again, appreciate the info.
Closed in favor of the meta-issue #9401.
Most helpful comment
@Ocramius Thanks for the detailed response. Makes sense; still sad from an end-user perspective but I understand the development need to remove areas that pose difficulties where the return is far less than the investment. Again, appreciate the info.