Add do_action hooks when rendering templates and template parts. ( #32309 ) #32316
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
I've added some calls to do_action() for two new action hooks:
rendering_template
andrendering_template_part
.These allow plugins / themes to develop extensions that will enable problem determination and/or logic associated with invocation context.
For example, I use these hooks to implement a debug block that will indicate which template has been used, the start and end of a template part and other information relevant during problem determination. See bobbingwide/sb-debug-block#2
How has this been tested?
I tested the changes by applying the
rendering_template
hook to Gutenberg v10.7.2 build, and therendering_template_part
hook to an override ofrender_core_block_template_part
in my ThisIs theme.Unfortunately I couldn't test using the latest extract from Gutenberg trunk since I could not get the build to work. Both
npm run dev
andnpm run build
fail. See bobbingwide/sb-debug-block#3Screenshots
Types of changes
Implements Feature Request #32309
Checklist:
*.native.js
files for terms that need renaming or removal).