[wp-meta] [Making WordPress.org] #1766: Handle hook deprecation in the DevHub theme
Making WordPress.org
noreply at wordpress.org
Sat Jun 11 16:38:58 UTC 2016
#1766: Handle hook deprecation in the DevHub theme
---------------------------+-----------------
Reporter: DrewAPicture | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: Developer Hub | Keywords:
---------------------------+-----------------
In #core10441, the core team is working on adding proper hook deprecation
in the form of two new functions: `apply_filters_deprecated()` and
`do_action_deprecated()`.
We'll obviously need to make some adjustments to
[https://github.com/WordPress/phpdoc-parser the parser] to properly route
the new function calls, but we also might need to adjust some minor things
in the !DevHub theme, such as ensuring the deprecation callout box can
handle a notice for hooks and corresponding replacement hook links.
Looks like we use `link_internal_element()` inside of `get_deprecated()`
to handle linking replacements, so in the interest of simplicity, we might
need to add an additional case for hooks referenced simply with
'hook_name'. This would be for the context of deprecated hook docs that
look like this:
{{{#!php
<?php
/**
* Some now-deprecated hook.
*
* @since 2.6.0
* @deprecated 4.6.0 Use 'replacement_hook' instead.
* @see 'replacement_hook'
}}}
We may very well already be in the clear, but it doesn't hurt to have a
tracking ticket here in case there's something we're missing.
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/1766>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list