Changes between Initial Version and Version 1 of Ticket #57487, comment 68
- Timestamp:
- 07/17/2023 11:17:56 PM (17 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #57487, comment 68
initial v1 13 13 Yes, there are few although I couldn't get the time to test and implement them. One is to change `_doing_it_wrong()` behavior (or the new proposed function that would replace it) depending on whether dev. mode is set. Thinking it may even throw a fatal error in some cases on a particularly "wrong" things. 14 14 15 Another is to reexamine all uses of `WP_DEBUG`, maybe make some of them conditional on dev. mode, and maybe make some throw more severe errors/warnings .15 Another is to reexamine all uses of `WP_DEBUG`, maybe make some of them conditional on dev. mode, and maybe make some throw more severe errors/warnings, perhaps with stack trace, etc. 16 16 17 17 > I'd propose that the default behavior for this function if no explicit mode is passed (i.e. $mode = null) would be to return true if wp_get_development_mode() returns any valid value rather than adding an explicit "any"