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.
Problem/Motivation
There's functions deprecated for removal in core 10
Proposed resolution
remove the usage, make sure no mentions left
Remaining tasks
review/commit
User interface changes
no
API changes
no
Data model changes
no
Release notes snippet
Comment | File | Size | Author |
---|---|---|---|
#31 | interdiff_3261245_28-31.txt | 2.7 KB | andregp |
#31 | 3261245-31.patch | 55.35 KB | andregp |
|
Comments
Comment #2
andypostComment #3
andypostNeeds views maintainer approaval
Comment #4
andypostProbably #3121008: Add test coverage for ViewsConfigUpdater could be closed
Comment #5
andypostfix CS
Comment #6
andypostComment #8
andypostNo idea where to point TODO but this function now no-op
Edit the issues should be kinda #3106666: Remove post updates added prior to 8.8.0
Comment #10
andypostinter-dependency issue
Comment #11
andypostComment #12
catchNeeds #3261486: Remove core updates added prior to 9.3.0 and adjust test coverage to land first.
Comment #13
andypostComment #14
andypostre-roll, probably it depends on #3261251: Remove deprecated node module functions
Comment #15
andypostthe plugin already removed from node module via https://www.drupal.org/node/2857891
I think the changes needs separate issue to remove remains on removed plugin, as there's extensive testing in core/modules/views/tests/modules/views_test_config/test_views/views.view.test_entity_test_link.yml
Comment #16
quietone CreditAttribution: quietone at PreviousNext commentedFound another one.
Comment #17
longwaveComment #19
longwaveUnrelated fail in QuickEditFileTest.
Comment #20
catchI think we should probably keep this in core with no tests methods, so it can be used for the next views update. There may already be one in 10.x since the patch was created.
Comment #21
andregp CreditAttribution: andregp at CI&T commentedBringing back ViewsConfigUpdaterTest::loadTestView as @catch suggested.
Obs.: The diff is a bit off because I had to do a small reroll (as views.view.test_user_multi_value.yml and ViewsConfigUpdaterTest.php had some alterations (commits) since last patch).
Comment #22
andregp CreditAttribution: andregp at CI&T commentedSorry, I didn't pay attention to the PHPStan check and missed an error.
use ($view)
was removed from ViewsConfigUpdater::updateAll since it wasn't being used, but the following line was added to updateAll on commit 9f17ffb15e (Issue #3173180).So I added back
use ($view)
to the method caller.Comment #24
andregp CreditAttribution: andregp at CI&T commentedThe only fail on patch #22 is:
Which was expected since @catch asked to "keep this in core with no tests methods" (#20) so sending back to NR.
Comment #25
paulocsShould a new Trait be created with the
loadTestView
function in this case?Comment #26
catchMaybe we could keep a stub test method with ::markTestSkipped() or a dummy assertion - the main reason to leave this in is because I am pretty sure we will need it again within weeks or at the most months.
Comment #27
paulocsAddressed #26.
Please review.
Comment #28
paulocsOps. I forgot to add 'test' before the function name.
Comment #30
daffie CreditAttribution: daffie commentedWe are removing this deprecation warning. Can the suppression of this warning be removed from tests/Drupal/Tests/Listeners/DeprecationListenerTrait.php?
The same for this deprecation warning. See previous item.
Comment #31
andregp CreditAttribution: andregp at CI&T commentedA new patch trying to address the points on #30
Comment #32
daffie CreditAttribution: daffie commentedAll my points have been addressed.
All code changes look good to me.
For me it is RTBC.
Comment #34
catchCommitted 55e559e and pushed to 10.0.x. Thanks!