- 🇷🇴Romania claudiu.cristea Arad 🇷🇴
Also
EntityRepository::loadEntityByUuid()
can be deprecated in favour of method that only needs the UUID, without the entity type argument - 🇩🇪Germany c-logemann Frankfurt/M, Germany
I completely disagree with the starting argument of 2016:
> Currently with Drupal 8 a UUID is useless.There are so much things we can solve with UUIDs like config entity conflicts and hiding serial IDs (see my module U3ID → . And since 2016 we have much more entity types including logs etc. and still growing. On larger systems this index would be a very huge table and should probably handled like a cache table which can be excluded in backups etc.
Personally I only see this as an interesting idea to find an entity just via UUID. But I hope this is something we won't be dependent on this feature in future because I see a lot of performance issues coming with it. So this should be optional at all or at least optional on any (!) entity type as an OPT IN setting in my opinion.