Project

General

Profile

Actions
Copy link

Feature #89836

closed

Do not auto-update PackageStates.php if ext folder is missing

Added by S P almost 5 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Extension Manager
Target version:
-
Start date:
2019-12-03
Due date:
% Done:

0%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

Consider this scenario:

  1. Dev has local environment
  2. Dev pulls latest git state with changed compsoer.json
  3. Dev opens Backend
  4. PackageState changes, because dev forgot to run composer install first and the core updated PackageStates due to missing ext-folders
  5. 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."

Actions
Copy link

Also available in: Atom PDF