Closed
Description
Ideally we need to allow lowest possible 2.x || ^3.0
. I guess we'll need to go for 2.4 as a minimum because of ReflectionEnum and annotation driver changes anyway.
Basing on https://github.com/doctrine/persistence/blob/3.0.x/UPGRADE.md:
- Removed
OnClearEventArgs::clearsAllEntities()
andOnClearEventArgs::getEntityClass()
- Deprecate DocumentManager::clear with an argument #2423 - removed
ObjectManagerAware
- not used directly in ODM - removed
AnnotationDriver
- Use colocated mapping driver #2420 Compatibility layer for AnnotationDriver #2443 - Removed
MappingException::pathRequired()
- not used directly in ODM - removed LifecycleEventArgs::getEntity() - method was deprecated for 10 years now (see Emit deprecation for LifecycleEventArgs::getEntity persistence#281), a note in UPGRADE will cut it
- removed support for short namespace aliases - we'll bring no compatibility layer for this
- removed ObjectManager::merge() - Deprecate DocumentManager::merge #2435
- removed support for doctrine/cache - Deprecate using doctrine/cache for metadata caching #2253
- changed signatures - we can't add types to method parameters while we still support 2.x
- Removed
PersistentObject
- not used directly in ODM
PR allowing || ^3.0
should mention in the upgrade notes that users may need to lock doctrine/persistence
themselves should they rely on functionalities that were removed, especially:
- removed LifecycleEventArgs::getEntity()
- removed support for short namespace aliases