#65434 closed defect (bug) (wontfix)
Coding Standards: Use strict null comparison instead of is_null()
| Reported by: | dervishov | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | General | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | Focuses: |
Description
Replace is_null() with strict null === comparison across core files, per WordPress Coding Standards.
GitHub PR: https://github.com/WordPress/wordpress-develop/pull/12124
14 files updated, 25 replacements. Full test suite passes.
Change History (2)
#1
@
6 weeks ago
- Focuses coding-standards removed
- Keywords good-first-bug has-patch removed
- Milestone Awaiting Review
- Resolution → wontfix
- Status new → closed
#2
@
6 weeks ago
Also, I'm not aware of is_null() being discouraged in coding standards. It's not documented here anyway: https://developer.wordpress.org/coding-standards/wordpress-coding-standards/php/
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
Hi @dervishov, welcome to WordPress Core Trac.
In general, WordPress is not interested in tickets like this. You can read more at https://make.wordpress.org/core/handbook/contribute/code-refactoring/