[wp-trac] [WordPress Trac] #31839: Setting error reporting level for wp_debug_mode

[WordPress Trac]

#31839: Setting error reporting level for wp_debug_mode
----------------------------+-----------------------------
 Reporter:  aifrim          |       Owner:
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:  Future Release
Component:  Bootstrap/Load  |     Version:  4.1.1
 Severity:  normal          |  Resolution:
 Keywords:  dev-feedback    |     Focuses:
----------------------------+-----------------------------

Comment (by aifrim):

 Replying to [comment:1 jeremyfelt]:
 > Hi @aifrim, thanks for the ticket!
 >
 > I don't think a `WP_DEBUG_LEVEL` would hurt, though I wouldn't want to
 encourage devs to silence messages that should be seen during development.
 Could removing strict notices be enough?
 >
 > Related: #24357, where the decision to show `E_STRICT` in PHP 5.4 was
 made (accepting that it may be too much).
 >
 > Also, an old duplicate of introducing some sort of log level constant
 exists in #14371, where it was decided at the time to let things be.

 Hy @jeremyfelt,

 First, I am sorry for not replying faster to your response. The
 notification email must have hit spam. You make valid points by not
 wanting to encourage developers to silence such messages during
 development.

 I made this ticket in order to get rid of the STRICT messages. I have been
 working a while on a project and it is still in development. Part of its
 code requires non strict programming and I have allowed WordPress to auto
 update because I want to launch it with the last available version of
 WordPress.

 So, how about a `WP_DEBUG_NONSTRICT` constant that disables `E_STRICT`
 warnings?

--
Ticket URL: <https://core.trac.wordpress.org/ticket/31839#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform