Make WordPress Core

Opened 2 years ago

Last modified 3 weeks ago

#47422 new enhancement

Coding Standards: wp-admin/includes/ms.php

Reported by: davidbaumwald Owned by:
Milestone: 5.9 Priority: normal
Severity: minor Version: 5.3
Component: Networks and Sites Keywords: has-patch good-first-bug
Focuses: multisite, coding-standards Cc:


Non-Yoda conditions, loose comparisons, loop/conditional assignments, unnecessary condition in wp-admin/includes/ms.php

Attachments (2)

47422.diff (5.6 KB) - added by davidbaumwald 2 years ago.
47422.1.diff (3.6 KB) - added by audrasjb 3 weeks ago.
Refreshes patch to handle loose comparisons

Download all attachments as: .zip

Change History (10)

2 years ago


#1 @davidbaumwald
2 years ago

  • Keywords has-patch added

#2 @spacedmonkey
2 years ago

  • Component changed from Administration to Networks and Sites
  • Milestone changed from Awaiting Review to Future Release

#3 @SergeyBiryukov
8 months ago

  • Keywords needs-refresh added
  • Milestone changed from Future Release to 5.8

Thanks for the patch!

It looks like some of these issues were resolved in [47219], [47808], and [47848], but there are still 13 loose comparisons in the file at the moment. A refresh would be helpful :)

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

5 months ago

#5 @davidbaumwald
5 months ago

  • Keywords good-first-bug added

#6 @desrosj
5 months ago

  • Milestone changed from 5.8 to Future Release

This one still needs a refresh. With 5.8 feature freeze today, I'm going to punt to Future Release. When a contributor is able to refresh the patch, it can be moved back to a numbered milestone.

#7 @SergeyBiryukov
5 months ago

  • Milestone changed from Future Release to 5.9

Moving to 5.9 just so that I don't forget about this ticket when working on other coding standard fixes :)

3 weeks ago

Refreshes patch to handle loose comparisons

#8 @audrasjb
3 weeks ago

  • Keywords needs-refresh removed

@SergeyBiryukov patch refreshed against trunk and also to handle the remaining loose comparisons. I kept 3 of them as I'm not sure it's a good think to cast the remaining '0' strings to integers.

Note: See TracTickets for help on using tickets.