Make WordPress Core

Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#31340 closed defect (bug) (invalid)

Use of the @subpackage tag in documentation

Reported by: henrywright's profile henry.wright Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: General Keywords:
Focuses: docs Cc:

Description

The documentation standards mention that the @subpackage tag should be used in all file header DocBlocks but the phpDocumentor docs consider the tag deprecated. See here.

Should I continue to use @subpackage when documenting plugins?

Change History (2)

#1 @DrewAPicture
10 years ago

  • Milestone Awaiting Review deleted
  • Resolution set to invalid
  • Status changed from new to closed

Hi Henry,

I would encourage you to use or not use @subpackage tags at your discretion.

Part of the issue we have in core is that our parser currently only supports phpDocumentor 1.0 in which name-spaced @package tags are not supported and @subpackage tags are not deprecated. Thus the note in the WordPress documentation standards.

When we opted to write our standard, we heavily leaned toward historical precedence of the code base, and that's something that we've maintained through today. The benefit of approaching change in this way is that later, when the PSR-5 recommendations are finalized and approved, it will be that much simpler for us to adjust to those new recommendations.

#2 @henry.wright
10 years ago

Thanks for the clarification, much appreciated.

Note: See TracTickets for help on using tickets.