#89836Do not auto-update PackageStates.php if ext folder is missing
Description
Consider this scenario:
- Dev has local environment
- Dev pulls latest git state with changed compsoer.json
- Dev opens Backend
- PackageState changes, because dev forgot to run
composer installfirst and the core updated PackageStates due to missing ext-folders - Dev has to fiddle around to get a correct state again
The core should only update PackageStates when explicitly an extension-related button is clicked or a command is executed or when the LTS version changed (e.g. upgrade 8 -> 9).
If there’s a mismatch between PackageStates and ext-Folders there should be just a warning without auto-altering the PackageStates file instead. Like “There’s a mismatch between configured and installed extensions, please check.”
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.