Replies: 1 comment 4 replies
-
|
It'd be really helpful if that section also listed the earliest hook at which you can call the function (when applicable). Also any other pre-conditions. That'd probably require annotating the source, but we could add the functionality to display it, and open a core/docs ticket for others to populate it. |
Beta Was this translation helpful? Give feedback.
-
|
Although, it may actually be better if instead Core would trigger a PHP notice/warning when it's called before it should be 🤔 |
Beta Was this translation helpful? Give feedback.
-
|
Core does have a number of places where |
Beta Was this translation helpful? Give feedback.
-
|
Hmmm, yeah. I guess in my workflow I go looking for "when should i..." before i start trying different actions. So maybe documenting it (in addition do There are also other places where those checks aren't added -- but probably should be -- like |
Beta Was this translation helpful? Give feedback.
-
|
I guess the docs would want to handle things like:
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
The only way to see a list of filters/actions present within a function is to expand the code block and read through.
There should be a dedicated list of filters (and their short description) present on the function page, linking to the hooks info page.
Beta Was this translation helpful? Give feedback.
All reactions