Closed destevetewis closed 2 years ago
I think it would be hard to remove these deprecations if we don't to break everything because it would need to require "doctrine/persistence": "^1.3.3"
.
We can maybe do it in master for the next version of API Platform.
WDYT @teohhanhui?
I suppose we don't want to prevent anyone from updating to the next patch version (e.g. for any security issues), so yeah, we have to do it in the next minor version.
I don't think doctrine/orm#7953 will remove all the deprecations we're seeing here. We need to make some changes in API Platform too.
We released a 1.3.4 of persistence and rolled back the deprecation messages coming from doctrine/orm
, and will only emit them when 1.4 is released. The idea is that all external code depends on doctrine/persistence
version ^1.3
and then the ORM and/or mongodb-odm
will raise to 1.4 in the near future when they are compatible. This way we will defer the deprecation messages until we ourselves are compatible.
Right now symfony returns multiple errors of deprecation related to doctrine persistence.
More information at https://github.com/doctrine/persistence/pull/82