Epic #84272: Use PSR-7 ServerRequestInterface in backend controllers
Decouple TreeController from UserSettingsController
[TASK] Decouple TreeController from UserSettingsController
Introduce a general wrapper for backend user configuration.
Reviewed-by: Christian Kuhn <firstname.lastname@example.org>
Tested-by: Christian Kuhn <email@example.com>
Reviewed-by: Anja Leichsenring <firstname.lastname@example.org>
Tested-by: Anja Leichsenring <email@example.com>
Tested-by: TYPO3com <firstname.lastname@example.org>
Reviewed-by: Andreas Wolf <email@example.com>
Tested-by: Andreas Wolf <firstname.lastname@example.org>
#2 Updated by Saskia Schreiber almost 2 years ago
- Subject changed from Use ServerRequestInterface in UserSettingsController to Refactor UserSettingsController to use a separate registry for user settings
The class UserSettingsController is currently a mixture of an ajax entry point and a registry for user related settings.
It provides an additional public method process() which is used inside the TreeController (to check for expanded pages).
This should be avoided as controllers should only provide proper actions as entry points.
Therefore there should be another class providing the settings for both UserSettingsController and TreeController.