[wp-meta] [Making WordPress.org] #1498: Developer code reference should include warnings for "@access private" functions
Making WordPress.org
noreply at wordpress.org
Fri Jan 29 16:21:02 UTC 2016
#1498: Developer code reference should include warnings for "@access private"
functions
--------------------------+---------------------------------------
Reporter: netweb | Owner: DrewAPicture
Type: enhancement | Status: accepted
Priority: normal | Component: developer.wordpress.org
Resolution: | Keywords: has-patch has-screenshots
--------------------------+---------------------------------------
Changes (by DrewAPicture):
* keywords: needs-patch => has-patch has-screenshots
* type: defect => enhancement
Comment:
Added [attachment:1498.diff]:
* Introduces a `get_private_access_message()` function to retrieve the
message
* Relocates a chunk of logic from
`DevHub_Formatting::make_doclink_clickable()` into a new
`DevHub_Formatting::get_internal_element_link()` method. This allows us to
reuse that logic for linking internal elements elsewhere
* Adds a single new CSS class, `private-access`
* Only handles displaying the message for private standalone functions and
hooks. Private methods fall under a different context in terms of
inheritance access.
See [attachment:1498_private_message.png] for what this would look like.
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/1498#comment:3>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list