Feature #89836
Do not auto-update PackageStates.php if ext folder is missing
Status:
New
Priority:
Should have
Assignee:
-
Category:
Extension Manager
Target version:
-
Start date:
2019-12-03
Due date:
% Done:
0%
PHP Version:
Tags:
Complexity:
Sprint Focus:
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 install
first 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."