[wp-meta] [Making WordPress.org] #5942: DevHub: Support viewing source on GitHub mirror
Making WordPress.org
noreply at wordpress.org
Thu Nov 4 09:06:08 UTC 2021
#5942: DevHub: Support viewing source on GitHub mirror
---------------------------+-----------------------
Reporter: netweb | Owner: dd32
Type: enhancement | Status: reopened
Priority: normal | Milestone:
Component: Developer Hub | Resolution:
Keywords: needs-patch |
---------------------------+-----------------------
Comment (by dd32):
Replying to [comment:7 coffee2code]:
> Replying to [comment:6 dd32]:
> > The above hook also shows a parser bug, as it's unable to extract the
PHP for the hook, this affects a number of hooks and functions that I've
seen over the last few months.
>
> Hooks are (and have always been) explicitly excluded**^*^** from having
their PHP source shown since doing so is not meaningful (it'd just be a
duplicate of the hook definition at the top of the page), so it merely
links to the source.
Huh, you're right.. okay that certainly makes sense.
Kind of seems weird that the source-code for the hook isn't displayed
within the "Source" heading though, given it's only a single line usually,
it might be worth duplicating it there?
> Functions should always show their source code though, so I'd be happy
to look into any that are failing to do so.
[https://developer.wordpress.org/reference/classes/twenty_fourteen_ephemera_widget/__construct/
twenty_fourteen_ephemera_widget::__construct] and similar theme class
methods are probably a good example, I'm sure I've seen another one but I
can't think of it off the top of my head.
[https://developer.wordpress.org/reference/classes/twenty_fourteen_ephemera_widget
the class definition] doesn't even exist
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/5942#comment:8>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list