In #2916740: Add generic entity actions → we want to mark some node and comment action plugins as deprecated and replace them with generic entity actions. Since #2870194: Ensure that process-isolated tests can use Symfony's PHPunit bridge to catch usages of deprecated code → landed, it's no longer possible to mark the complete action plugin class as deprecated, because during tests, the plugin discovery will still call this class and trigger the deprecation error.
For example the NodeActionsConfigurationTest test opens up the UI and as part of that the deprecated plugin will be initialized.
So we need an other solution to mark plugins as deprecated.
I discussed this shortly with berdir and alexpott on IRC and a first proposal is to add a "deprecated" key into the plugin annotation and call trigger_error during Drupal\Component\Plugin\PluginManagerBase::createInstance()
Discuss
Implement
Review
Commit
Update
https://www.drupal.org/core/deprecation →
None
None
None
Needs work
11.0 🔥
Last updated
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
It could use new attribute for plugin classes https://wiki.php.net/rfc/deprecated_attribute
The new native #[\Deprecated] attribute in PHP 8.4 can automatically throw deprecation messages, so external libraries can give unexpected deprecations