Bug: Do not set debug constants

[slaFFik]

Either ask the user to set them, or at least wrap your own code into the if ( !defined() ) checks.

I'm talking about these:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_DISPLAY', false );
define( 'WP_DEBUG_LOG', true );

Otherwise every app launch on a WP install just creates errors for me because I already have those constants set like that at the beginning of the file:

const WP_DEBUG         = true;
const WP_DEBUG_LOG     = true;
const WP_DEBUG_DISPLAY = true;
const SAVEQUERIES      = true;
const SCRIPT_DEBUG     = true;

[jonathanbossenger]

This is a good point, thanks. I prefer to automatically set the debug constants, so I think I'll defer to if ( !defined() ) checks for now. However, it might be useful to add some Settings later on, and allow users to disable certain defaults.

[slaFFik]

Just a reminder about this issue - because it's blocking me from using WP Debug more often (I don't always want to edit wp-config.php every time I want to launch WP Debug app).

[slaFFik]

You may also consider not assuming that developers are using define() function to set those constants (see here

wp-debug/main/index.js

Line 432 in 2aabd4f

`\ndefine( '${name}', ${originalValue} );\n`

), because const is totally valid and imo a cleaner way to do that.

[jonathanbossenger]

@slaFFik as discussed last year, I'm working on a possible "paid" version of the app, which includes some of these additional features. I've invited you to that repo to help me beta test it.