WordPress.org
Get WordPress

Making WordPress.org

Opened 11 years ago

Closed 10 years ago

Last modified 21 months ago

#177 closed enhancement (duplicate)

Add cross referencing throughout code reference

Reported by: samuelsidler's profile samuelsidler Owned by:
Milestone: Priority: normal
Component: Developer Hub Keywords: has-patch
Cc:

Description

The code reference should cross reference itself. e.g., hooks that appear inside of a function, or functions attached to hooks.

Change History (10)

#1 @samuelsidler
11 years ago

  • Priority changed from low to normal

#2 @siobhan
11 years ago

  • Cc siobhan added

#3 follow-ups: @toscho
11 years ago

  • Cc toscho added

One simple way to find related related posts would be the Trac ticket number. In some docs, this number is available, so we could store its value in a post meta field. Unfortunately, there seems to be no standard. I found four different variants in wp-includes/functions.php:

// see http://core.trac.wordpress.org/ticket/9396

<!DOCTYPE html>
<!-- Ticket #11289, IE bug fix: /* snip */
-->

 * See http://core.trac.wordpress.org/ticket/8497

 * @link http://core.trac.wordpress.org/ticket/19589

It would be nice to have a standard. We could extend the PHP doc standard with a new tag and a vendor prefix:

 * @wp-ticket http://core.trac.wordpress.org/ticket/19589

Not sure what the best place is to discuss that topic. Make? Core trac? Chat? This trac?

#4 in reply to: ↑ 3 @samuelsidler
11 years ago

Replying to toscho:

Not sure what the best place is to discuss that topic. Make? Core trac? Chat? This trac?

Bring it up with the inline docs team and see what they think. Best way to do that is attend their weekly meeting or comment on their weekly update on make.

#5 in reply to: ↑ 3 @kpdesign
11 years ago

Replying to toscho:

It would be nice to have a standard. We could extend the PHP doc standard with a new tag and a vendor prefix:

 * @wp-ticket http://core.trac.wordpress.org/ticket/19589

Not sure what the best place is to discuss that topic. Make? Core trac? Chat? This trac?

All links to Trac tickets and other external documentation will be handled using the @link tag in the doc blocks. References to other functions/classes/hooks/etc. will be done using the @see tag.

We are trying to stay away from using any custom tags in the doc blocks.

We're aware of the inconsistencies, and are working hard to fix them.

You, and anyone else, are always welcome to attend our weekly inline docs chat, Wednesdays at 18:00 UTC in #wordpress-sfd, or reach out to @DrewAPicture or myself with questions in between meetings. :)

#6 @trishasalas
10 years ago

  • Cc trisha@… added

#7 @RMarks
10 years ago

  • Cc rmarks@… added

This ticket was mentioned in ​Slack in #meta-devhub by siobhan. ​View the logs.
10 years ago

#9 @siobhan
10 years ago

  • Resolution set to duplicate
  • Status changed from new to closed

Duplicate of #323.

This ticket was mentioned in ​PR #178 on ​WordPress/wporg-main-2022 by ​@adamwood.
21 months ago #10

  • Keywords has-patch added

Fixes #177

Props @tellthemachines, @StevenDufresne

### How to test the changes in this Pull Request:

1.
2.
3.

Note: See TracTickets for help on using tickets.