Module configuration cache file is not removed on development mode change #5
Labels
Bug
Something isn't working
Comments
XCame
pushed a commit
to XCame/laminas-development-mode
that referenced
this issue
Aug 2, 2023
When searching for the config dir location, isset always returned true for projectDir since it was an empty string by the constructor defaults, resulting in a file exists on /config/application.config instead of config/application.config Signed-off-by: Fabian Kreuzkam <fk@herold-schoensteiner.de>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When enabling/disabling development mode, the module cache file is not removed. On investigation, it seems this is because the application configuration returned by
getApplicationConfig()inConfigDiscoveryTraitis an empty array, which in turn is because the application configuration file is not being read in correctly.Other functionality (addition/removal of
development.*.distfiles) is fine.Originally posted by @vvaswani at zfcampus/zf-development-mode#22
The text was updated successfully, but these errors were encountered: