Make WordPress Core

Opened 3 months ago

Closed 3 months ago

#63889 closed defect (bug) (duplicate)

Twenty Sixteen: Correct DocBlock tag order for @since and @global

Reported by: viralsampat's profile viralsampat Owned by:
Milestone: Priority: normal
Severity: trivial Version:
Component: Bundled Theme Keywords: has-patch
Focuses: coding-standards Cc:

Description

Hello Team,

While reviewing the WordPress theme files, I noticed that in the Twenty Sixteen theme’s functions.php file, the DocBlocks contain @since and @global tags that are not in the correct order according to the WordPress documentation standards.

To maintain consistency and follow the WordPress guidelines, the order of these tags should be corrected.

I also reviewed existing core tickets and found similar tickets where DocBlock adjustments and tag order corrections were addressed. This update would help keep the documentation clean and standardized.

Thanks,

Attachments (3)

63889.patch (731 bytes) - added by viralsampat 3 months ago.
I have checked above mentioned issue and resolved it. Here, I have added my patch.
63889.2.patch (731 bytes) - added by viralsampat 3 months ago.
I have checked above mentioned issue and resolved it. Here, I have added my patch.
63889.3.patch (592 bytes) - added by sabernhardt 3 months ago.

Download all attachments as: .zip

Change History (6)

@viralsampat
3 months ago

I have checked above mentioned issue and resolved it. Here, I have added my patch.

@viralsampat
3 months ago

I have checked above mentioned issue and resolved it. Here, I have added my patch.

#1 @sabernhardt
3 months ago

  • Keywords dev-feedback 2nd-opinion needs-testing removed
  • Severity changed from normal to trivial

The asterisk (*) should not have any spaces at the end of the line. When submitting a pull request, the coding standards GitHub action would warn about extra spaces.

63889.3.patch removes spaces and the unnecessary line below the global.

#3 @sabernhardt
3 months ago

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

Duplicate of #58715.

Thanks for catching that! It's already part of PR 5920.

Note: See TracTickets for help on using tickets.