Problem/Motivation
In #3582610: Rename gin in comments, Gin references in comments were renamed.
Seems like the gin_preprocess_ or other gin_ mentions in comments were missed/skipped. We should correct these to point to the correct hook names. For example:
- gin_preprocess_block_content_add_list
- gin_form_node_form_alter
- ...
There seems to be 24 occurences of gin_ hooks references in comments. Plus 2 references to gin_actions (link) and gin_sidebar (link) (but these two are questionable, as there are still form elements with the same names, so probably something for another issue).
Steps to reproduce
Proposed resolution
Find all occurences and replace to correct hooks names.
Remaining tasks
User interface changes
Introduced terminology
API changes
Data model changes
Release notes snippet
Comments
Comment #4
quietone commented@poker10, thanks for making this issue.
Comment #5
sivaji_ganesh_jojodae commentedThe usage of parentheses with
@seeis inconsistent.Some lines opt for
@see \Drupal\default_admin\Hook\PreprocessHooks::preprocessInput()Others in Drupal sometimes use:
@see ...::preprocessInputComment #6
needs-review-queue-bot commentedThe Needs Review Queue Bot tested this issue. It fails the Drupal core commit checks. 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 #7
nod_Comment #8
quietone commented@sivaji_ganesh_jojodae, thanks. I did forget to add the "()" at the end.
Comment #10
smustgrave commentedApplied the MR and did a phpstorm search for gin_ and all instances referencing hooks appears to be replaced.
Applied 3 missing (), rest LGTM.
Comment #11
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 #12
sivaji_ganesh_jojodae commentedI've resolved merge conflicts and rebased the branch.
Comment #13
dcam commentedThe rebase appears to be correct. It's kind of a pain to figure it out because part of the commit history is inaccessible now. But I did my best to check it based on the couple of pre-rebase commit links that are accessible from here in the issue log. I did a before/after comparison of the code. Nothing looks out of place. So I think this is good to be RTBC again.
Comment #15
amateescu commentedCommitted 3301cb4 to main and 034e955 to 11.x. Thanks!