Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Another easy one, properly deprecating a bunch of methods that are already used, two from EntityTypeRepository, useCaches() which had one usage left, as well as createInstance() and getInstance(), those are not broken anyway and nobody can be calling them :)
Comment | File | Size | Author |
---|---|---|---|
#8 | entity-manager-unused-3028671-8-interdiff.txt | 860 bytes | Berdir |
#8 | entity-manager-unused-3028671-8.patch | 20.63 KB | Berdir |
#6 | entity-manager-unused-3028671-6.patch | 19.79 KB | Berdir |
#3 | entity-manager-unused-3028671-3.patch | 20.31 KB | Berdir |
#2 | entity-manager-unused-3028671-2.patch | 9.18 KB | Berdir |
Comments
Comment #2
BerdirComment #3
BerdirSlightly expanding the scope and including the last installed methods which are also almost completely updated yet. This will fail with tons of deprecation messages as it depends on #3025427: Add @trigger_error() to deprecated EntityManager->EntityTypeBundleInfo methods to update the entity storage handlers.
Comment #6
BerdirAand the blocker is in, quick reroll.
Comment #8
BerdirMissed one call.
Comment #9
martin107 CreditAttribution: martin107 as a volunteer commentedWhile subtle I think this code change enhances the developer experience....so plus one on the idea behind the issue.
I have had a slow visual scan of this patch...
All change, appear to be implemented cleanly - and match the single minded focus behind the issue.
Comment #10
catchCommitted f49d8f1 and pushed to 8.7.x. Thanks!