WordPress.org

Making WordPress.org

Opened 6 years ago

Closed 5 years ago

Last modified 5 years ago

#323 closed task (fixed)

Used by and Uses information to be added to code reference archive pages

Reported by: siobhan Owned by: coffee2code
Milestone: Priority: normal
Component: Developer Hub Keywords: has-patch needs-testing
Cc:

Description

Currently the archive pages have a TODO note beside Used by and Uses. This information needs to be pulled from the parser and the number of functions Used by and Uses should be displayed. The user should be able to click on these and it bring up an archive page of everything that is used by or that uses the function etc.

Currently looks like:

https://i.cloudup.com/VPUWkwHbf6.png

It should display information as in the bottom right here:

https://i.cloudup.com/9yn5kGyqna.png

Remove the number of examples for now. This will need to be pulled from WordPress and we don't have functionality for adding examples yet.

Attachments (4)

323.diff (6.0 KB) - added by atimmer 5 years ago.
Screen Shot 2014-10-12 at 15.09.16.png (221.8 KB) - added by atimmer 5 years ago.
Screen Shot 2014-10-12 at 15.09.09.png (105.1 KB) - added by atimmer 5 years ago.
323.2.diff (15.2 KB) - added by atimmer 5 years ago.

Download all attachments as: .zip

Change History (20)

#1 @siobhan
6 years ago

  • Owner set to Rarst
  • Status changed from new to assigned

#2 @siobhan
6 years ago

We are waiting for feedback from @coffee2code about whether we can use posts2posts on wordpress.org

#3 @siobhan
6 years ago

We're able to use posts2posts on WordPress.org. @Rarst is investigating whether we should bundled it or whether the parser should run alongside it.

@atimmer
5 years ago

#5 @atimmer
5 years ago

  • Cc services@… added

323.diff is a first pass on 'uses' and 'used by' on the single pages, more to come later.

For the parser the following branch can be used: https://github.com/atimmer/WP-Parser/tree/p2p-relationships. I have not yet made a pull request because I am not yet happy with the code.

@atimmer
5 years ago

#6 @atimmer
5 years ago

  • Keywords has-patch needs-testing added
  • Type changed from defect to task

Added 323.2.diff which adds the used/used by to the archive and improves it on the single page.

Initially there are now 5 uses/used by shown and you can click the "Show 19 more used by" link to show them. You can probably come up with better text for that.

I also added two screenshots so you can shoot on them without needing to have a local env.

Last edited 5 years ago by atimmer (previous) (diff)

#7 @siobhan
5 years ago

#494 was marked as a duplicate.

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


5 years ago

#9 @siobhan
5 years ago

  • Owner changed from Rarst to coffee2code

#10 @siobhan
5 years ago

#177 was marked as a duplicate.

This ticket was mentioned in Slack in #meta-devhub by coffee2code. View the logs.


5 years ago

This ticket was mentioned in Slack in #meta-devhub by atimmer. View the logs.


5 years ago

#13 @coffee2code
5 years ago

In 1194:

developer.wordpress.org: Register P2P post relationships. See #323.

#14 @coffee2code
5 years ago

  • Resolution set to fixed
  • Status changed from assigned to closed

In 1196:

developer.wordpress.org: Add 'Used By' and 'Uses' sections to parsed content permalink pages.

Basically the UI surfacing of the P2P relationships.

Fixes #323.
Props atimmer.

#15 @coffee2code
5 years ago

In 1197:

developer.wordpress.org: Responsive improvement for 'Uses' when it falls below 'Used by'. See #323.

#16 @coffee2code
5 years ago

Changes from 323.2.diff by @atimmer as committed in [1196]:

  • Removed space between function name and '()' in Uses section
  • Added '()' after function names in Used By section
  • Changed use of strong tag to span tag for filenames in Uses/Used By sections
  • Moved Used By/Uses section to just before Source (putting it after Parameters, Explanations, Methods)
  • Tweaked responsive styling
  • Translated more strings
  • Removed introduction and use of mixins.css (by setting section { overflow: auto; } instead
Note: See TracTickets for help on using tickets.