Closed (fixed)
Project:
Drupal core
Version:
11.x-dev
Component:
base system
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
17 Mar 2025 at 14:09 UTC
Updated:
22 May 2025 at 22:14 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
nicxvan commentedComment #4
nicxvan commentedI am still working on this.
Comment #5
nicxvan commentedComment #6
nicxvan commentedI am still working through this.
Comment #7
nicxvan commentedComment #8
nicxvan commentedComment #9
nicxvan commentedComment #10
nicxvan commentedComment #11
smustgrave commentedNot sure I'm following the need to break up into 2 file locations now?
Comment #12
nicxvan commentedWhen it's for phase runtime or update they are hooks still so those go in the Hook namespace.
If they are install time then that is not a hook, it is a special class, the change record is here: https://www.drupal.org/node/3492429
Comment #13
smustgrave commentedGotcha
Comment #14
dwwMostly looks good, thanks! A few nits.
Comment #15
nicxvan commentedApplied almost all of them, I probably would have left most of those to follow ups since copy and paste issues like this are already hard enough to review.
I left one I didn't think was correct.
Comment #16
dwwSorry, my 😉 about adding StringTranslationTrait was shorthand for "add this, then use it". But you only added, so phpcs is complaining about unused use. Can either revert that suggestion, or actually use the trait...
Thanks,
-Derek
Comment #17
nicxvan commentedAh sorry, for some reason I was looking at the wrong class you removed the extra return, I applied that locally.
I also removed the string translation, I saw the other translation change and thought it was the complete suggestion.
I decided to remove it since this is part of the install time, and it's better to handle those updates in a follow up I think. For the bits that are outside of install time I think it's ok to add injection here.
Comment #18
dwwCool, thanks!
New day, fresh eyes, new MR threads. 😂
Comment #19
nicxvan commentedCreated the follow ups for the ones I think are out of scope.
Addressed other comments.
Ready for review again!
I'll keep an eye on tests.
Comment #20
dwwThanks for those follow-ups. Resolved all the open threads with links. Re-reviewing now.
Comment #21
dwwWith all the follow-ups open, all my concerns have been addressed. I see no way to further improve this MR that's in scope. The pipelines are all green. RTBC!
Thanks,
-Derek
Comment #22
needs-review-queue-bot commentedThe Needs Review Queue Bot tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".
This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.
Comment #23
smustgrave commentedAppears to be random nightwatch failure, re-running is fine
Restoring previous RTBC status.
Comment #24
larowlanOne comment about duplication
Comment #25
dwwReplied re duplication. Back to RTBC.
Comment #26
dwwSorry, wrong link. See related issues.
#3520890: Reduce pgsql requirements duplication
Comment #29
larowlanCommitted to 11.x and unpostponed the follow up
Thanks
Comment #30
dwwThanks!
Giving this its proper parent issue for posterity...