- Issue created by @catch
- Merge request !11019Move the file formatter base classes out of the formatter plugin namespace. → (Open) created by catch
- 🇬🇧United Kingdom catch
MR is green, but we need to figure out what the bc layer looks like here.
Either:
1. Leave subclasses of the moved classes, issue a deprecation in the constructor(?)
2. class_alias somewhere.
I also wondered if we could create an extra classloader that handles deprecating a class, taking a list of classes and replacements from the container, and having DrupalKernel add it somewhere.
The classloader could decorate the composer classloader, when it's passed a deprecated class, it compares against the array of deprecated classes, if it's in there, triggers a deprecation message and then passes the replacement classname to the composer classloader, otherwise just fall through.
This would be nearly as light as a class_alias when we want to move a class, but would allow us to eventually remove items from the list in major releases instead of keeping class_alias around permanently.
For this issue of plugin discovery, it would also mean we can immediately stop scanning these classes during discovery.