[wp-trac] [WordPress Trac] #19451: Cannot distinguish which WordPress Signup stage I am
WordPress Trac
noreply at wordpress.org
Thu Sep 19 20:53:14 UTC 2013
#19451: Cannot distinguish which WordPress Signup stage I am
----------------------------------+------------------
Reporter: Cimmo | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: 3.7
Component: Multisite | Version: 3.3
Severity: normal | Resolution:
Keywords: has-patch needs-docs |
----------------------------------+------------------
Comment (by nacin):
Replying to [comment:13 DrewAPicture]:
> Replying to [comment:12 jeremyfelt]:
> > This makes more when a hook is used multiple times in one function. A
little less when we're dealing with hooks in 3 different functions. If we
use `//duplicate hook`, should it also point to the function where the
hook is documented?
>
> Nope. `//duplicate_hook` is the grep-able solution nacin came up with. I
have the impression all the duplicate hooks will be tied together with
their primaries via some kind of magic on the other end.
Basically, rather than re-documenting the same hook in multiple places, I
figured something simple like this would be much easier to study our
duplicate hooks and make a determination on what to do. We'll need to make
sure "duplicate" filters are actually used in similar contexts, receive
the same arguments, etc. Yes, we'll probably only document a hook once in
a function, and yes, we'd like to document even a duplicate hook that is
elsewhere (just because we're pulling it into the code reference doesn't
mean inline documentation shouldn't also serve its purpose as informing a
reader of the code). This just tries to punt on that for the moment.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/19451#comment:14>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list