Introduce 'debug' as an option for UF_MODE

[Silic0nS0ldier]

Currently there is a dev UF_MODE that favours itself to development. While this works good, sometimes we need more verbosity to track down the source of an error.

I suggest we introduce a third UF_MODE called debug that puts everything in debug mode.

It may also be of benefit to make it such that this mode can be used alongside other modes, such as production, to help isolate issues specific to that mode (since there are performance related differences).

[lcharette]

Can't it be set in dev/production specific config files?

[alexweissman]

I think that's @Silic0nS0ldier's point. We have a debug.php config file that just opens up the floodgates, turning on all debug settings.

[anderson2927]

Nemesis, we meet again

[Silic0nS0ldier]

Noticed that UF has grown a testing.php. Would I be correct in assuming this knew file introduces the features wanted in a debug.php configuration?

[lcharette]

testing is used to disable stuff like cache and displayErrorDetails when running PHP Unit tests

[Silic0nS0ldier]

Ah. That clears things up.

[alexweissman]

There's also a dev.php. Can we rename this to debug.php instead? So-called "dev" mode is really just the default mode.

[lcharette]

Note that when Bakery creates app/.env, it set UF_MODE to "".

To make dev truly the default mode, bakery needs to be updated

[alexweissman]

Well, right now "" is equivalent to default: https://github.com/userfrosting/config/blob/master/src/ConfigPathBuilder.php#L35-L39

[lcharette]

So-called "dev" mode is really just the default mode.

dev == default?

On a side note, It could be clearer for new dev if something was defined in .env instead of ""...

[alexweissman]

default == default

My point is, there is no explicit "dev" mode right now. That dev.php should really be called debug.php.

[lcharette]

Done in ec508e0 for 4.2