Docs: Correct hook name from abilities_api_init to wp_abilities_api_init
#133
Conversation
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## trunk #133 +/- ##
=========================================
Coverage 80.39% 80.39%
Complexity 178 178
=========================================
Files 20 20
Lines 1474 1474
Branches 120 119 -1
=========================================
Hits 1185 1185
Misses 289 289
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
gziolo
added
the
[Type] Developer Documentation
2 participants
Description
This PR fixes inconsistent hook naming in the documentation. The documentation was showing
abilities_api_initbut the actual hook fired by the codebase iswp_abilities_api_init.Fixes: #132
Changes
docs/getting-started.mdto use correct hook namedocs/intro.mdto use correct hook nameWhy This Change?
All PHP code and tests use
wp_abilities_api_init:WP_Abilities_Registry::get_instance()(line 294)wp_register_ability()(line 272)docs/hooks.mdanddocs/php-api.mdThe two files updated in this PR were the only documentation files with the incorrect hook name.