laminas / laminas-development-mode

Laminas development mode script
BSD 3-Clause "New" or "Revised" License
17 stars 9 forks source link

Why development.local.php? #3

Open weierophinney opened 4 years ago

weierophinney commented 4 years ago

Why does zf-development-mode need to bother switching development.local.php in and out when development.config.php adds globs for *.local-development.php?

In other words, whatever I want to put in development.local.php I could just put in local-development.php, and it would only get included when I'm in development mode.

Just seems like two files are being switched and out when only one is needed...


Originally posted by @bitwombat at https://github.com/zfcampus/zf-development-mode/issues/33

haclong commented 1 month ago

well, when development mode is enabled,

"development.config.php" says development config files should be "*.local-development.php" but does not mention "development.local.php".

this is verified because i have changed "display_exceptions" value in "view manager" and the new value is not taken into account.

If i changed development.local.php into development.local-development.php, then my changes are taken into account.

i have changed the 'config_glob_paths' in development.config.php file and added the 'autoload/development.local.php' but it doesn't seem to work either.

THE WORKAROUND -> i can't change development.config.php : i couldn't find the right way to add "autoload/development.local.php" file into the "config_glob_path" -> i have copied the "development.local.php" into "development.local-development.php" in order to have the development config taken into account -> i leave the "development.local.php" which is a duplicate of "development.local-development.php" because when i enable the development-mode, the script will create it again anyway...

WHAT I WANT 1/ make it work with "development.local.php" 2/ or make it consistent with "development.config.php" and use "*.local-development.php" filename format.