Problem/Motivation
Drupal 11 introduced object-oriented hook implementations via the #[Hook] attribute (change record). Converting the module's procedural hooks to an OOP hook class improves structure and aligns with Drupal core. An MR is opened per branch as needed.
Steps to reproduce
Proposed resolution
Move hook_preprocess_menu() from varbase_blog.module into src/Hook/VarbaseBlogHooks.php with a #[Hook] attribute. No #[LegacyHook] wrapper (Drupal ~11.4-only).
Remaining tasks
- ✅ File an issue about this project
- ✅ Addition/Change/Update/Fix to this project
- ✅ Testing to ensure no regression
- ➖ Automated unit/functional testing coverage
- ➖ Developer Documentation support on feature change/addition
- ➖ User Guide Documentation support on feature change/addition
- ➖ UX/UI designer responsibilities
- ➖ Accessibility and Readability
- ✅ Reviewed by a human
- ✅ Code review by maintainers
- ✅ Full testing and approval
- ✅ Credit contributors
- ✅ Review with the product owner
- ✅ Update Release Notes
- ✅ Release varbase-9.2.0, varbase_blog-9.2.0
User interface changes
- N/A
API changes
- N/A
Data model changes
- N/A
Release notes snippet
task: #3608319 Remove the #[LegacyHook] shims for full OOP hooks
Issue fork varbase_blog-3608319
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
rajab natshah✅ Released varbase_blog-9.2.0
Comment #8
rajab natshah✅ Released varbase-9.2.0
Comment #9
rajab natshahComment #10
rajab natshah✅ Released varbase_blog-10.1.1