How to best handle documentation around new OOP hooks

Created on 8 January 2025, 2 months ago

Problem/Motivation

Mentioned in 📌 Create class to replace hook_install_requirements Active

That's good, but we'd still be losing the discoverability of it in the documentation as an API.

With hooks, there is a @hooks topic that explains the concept and lists the API elements. With HookyClasses, you only learn of a particular class if you happen to stumble on it.

Steps to reproduce

N/A

Proposed resolution

TBD

Remaining tasks

Determine new approach

User interface changes

Introduced terminology

API changes

TBD

Data model changes

Release notes snippet

📌 Task

Status

Active

Version

11.0 🔥

Component

base system

Created by

🇺🇸United States smustgrave

Live updates comments and jobs are added and updated live.

11.2.0 release priority

Comments & Activities

Issue created by @smustgrave
Comment 2 months ago →
🇺🇸United States nicxvan
We already have ✨ Support for OO hooks implementations in classes Postponed for the hooks.

The question @joachim had #3490843-18: Create class to replace hook_requirements('install') → is more about the install time which will no longer even be a hook.

We can still track that here. I think the only way to solve it is to create a documentation page, or maybe something to grab providers?

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024