- Issue created by @dww
- πΊπΈUnited States dww
Drupal\update\UpdateManagerInterface
is a pain, andUpdateManagerInterface::NOT_SECURE
and friends are sprinkled throughout.This might be more trouble than it's worth. From a Slack thread today:
https://drupal.slack.com/archives/C079NQPQUEN/p1745370644226489dww: It's not totally clear to me why this is even a service.
larowlan: We have a moved class autoloader in core now, search for - you can define a container param with modulename.moved_classes that will load the new name - see core.moved_classes in core.services.yml for an example
larowlan: You can also add deprecated to service definitions - see library.discovery.collector in core.services.yml
so I think they should handle the service name and the class names - i.e. I think we have the tools for this now
dww: Thanks for those details!
dww: Stepping back a bit -- is this even worth it?
dww: Maybe "no one" cares that this service / interface have this name, even if it doesn't really "manage" anything?
larowlan: :shrug: naming is hard
larowlan: Maybe something to ask the UX team - package manager is working to rename 'Stage' to 'Sandbox' in class names out of feedback from the UX team even though its really only DX
moshe: i vote for not worth it