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.
A separate issue was required during development of #2273381: Convert ContextAwarePluginBase to traits due to the out-of-scope changes to testing infrastructure required to be able to perform this deprecation.
Ideally the goal is to deprecate \Drupal\Component\Plugin\ContextAwarePluginBase
and \Drupal\Component\Plugin\ContextAwarePluginInterface
so that we don't have competing implementations in component and core namespace (background).
Comment | File | Size | Author |
---|---|---|---|
#11 | 3153852-component-test.patch | 966 bytes | catch |
Issue fork drupal-3153852
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #6
catchMoving this back to active. I think since we already deprecated the Drupal\Core version and everything around it, we should just add the docs to 9.4 and 9.5 and be done with it.
Comment #7
clayfreemanUpdating issue title to more accurately reflect what's needed.
Comment #9
clayfreemanComment #10
catchReal test failure, one of the patches in #2273381: Convert ContextAwarePluginBase to traits (before this hunk was removed) has a fix for it.
Comment #11
catchExtracted the ComponentTest change from #2273381: Convert ContextAwarePluginBase to traits
Comment #12
longwaveThe MR is passing, so not sure why #11 is needed. The deprecation notices look OK to me.
Comment #13
catch@longwave the patch is for this test failure from #8.
https://www.drupal.org/pift-ci-job/2403778
Not sure why it failed there but passed for the MR.
Comment #14
clayfreeman@catch
For clarity: my original commit in the merge request failed with that message, but I amended my commit and did a force push to remove any mention of
Drupal\Core
in the deprecation notice and instead declared that there was no replacement (because there truly isn't one at the component-level).The MR is now passing because of this change, so the patch from #11 shouldn't be necessary.
Comment #17
catchOhhhhh that explains it!
Committed/pushed to 10.0.x and cherry-picked to 9.5.x, thanks!