Make WordPress Core

Opened 6 years ago

Last modified 16 months ago

#52888 reviewing enhancement

Docs: Update get_children function

Reported by: ribaricplusplus Owned by: SergeyBiryukov
Priority: normal Milestone: Future Release
Component: Posts, Post Types Version:
Severity: minor Keywords: has-patch dev-feedback
Cc: Focuses: docs

Description

get_children documentation is very confusing to read, an entire essay for what could be said in a single paragraph, so I've rewritten it.

Attachments (1)

52888.diff​ (3.5 KB ) - added by ribaricplusplus 6 years ago.

Download all attachments as: .zip

Change History (13)

#1 @mukesh27
6 years ago

  • Keywords has-patch added
  • Summary Fix get_children documentation → Docs: Update get_children function

#2 @SergeyBiryukov
6 years ago

  • Component General → Posts, Post Types
  • Milestone Awaiting Review → 5.8

#3 @SergeyBiryukov
6 years ago

  • Owner set to SergeyBiryukov
  • Status new → reviewing

#4 @desrosj
5 years ago

  • Milestone 5.8 → 5.9

This is a documentation only change, which can be included during the beta part of the release cycle. But I'd like to understand why this description is so long, and if there are any historical reasons for any of the callouts in this docblock. I'm punting to 5.9, but if someone is able to tackle this during 5.8 beta, it can be moved back.

This ticket was mentioned in ​Slack in #core by audrasjb. ​View the logs.


5 years ago

This ticket was mentioned in ​Slack in #core by audrasjb. ​View the logs.


5 years ago

#7 @hellofromTonya
5 years ago

  • Milestone 5.9 → 6.0

While the docblock is long, if it provides context and better understanding, then it's worth having it remain in place. That said, I agree with @desrosj, an exploration is needed to first understand if there are historical reasons and if the context does actually lean into better understanding.

With 5.9 RC1 tomorrow and no movement on this ticket since 5.8, moving it to 6.0.

#8 @ribaricplusplus
5 years ago

In my opinion, the longer documentation does not provide better understanding. Wouldn't have rewritten it otherwise. For example, the entire discussion about "we could make attachments the child of a post but nah this is no longer accurate" is irrelevant and just confuses anyone who reads this.

#9 @costdev
4 years ago

  • Milestone 6.0 → 6.1

While this is a documentation-focused ticket, it is quite a large change from the original documentation.

The discussion about whether this change should be made is still being discussed, so I'm going to move this to the 6.1 milestone for now.

If anyone feels that this ticket has moved towards being committed before 6.0 RC1, feel free to bring it back into the milestone for commit consideration.

#10 @davidbaumwald
4 years ago

  • Keywords dev-feedback added
  • Milestone 6.1 → Future Release

With 6.1 Beta 1 releasing tomorrow and this ticket still needing discussion and a decision about whether to actually update this docblock, this is being moved to Future Release.

If any maintainer/committer wishes to assume ownership of this during a specific cycle, feel free to update the milestone at that time.

This ticket was mentioned in ​PR #9097 on ​WordPress/wordpress-develop by ​@sainathpoojary.


16 months ago
#11

Trac ticket: #52888

#12 @sainathpoojary
16 months ago

Refreshed patch to apply cleanly against the latest trunk.

Note: See TracTickets for help on using tickets.