Implement postprocessing and validation into the configuration manager
|Priority:||Should have||Due date:|
|Assignee:||Robert Lemke||% Done:||
|Target version:||TYPO3 Flow Base Distribution - 1.0 alpha 7|
The Configuration Manager should provides some kind of hooks to allow the different submodules of FLOW3 to postprocess and validate their configuration.
Currently this postprocessing is done directly in the Configuration Manager (where it doesn't belong) and validation is done during runtime in the sub modules (which is unnecessary because cached configuration doesn't need to be validated again).
[-API] FLOW3 (Configuration): Removed the Configuration Manager's getSettings() method! If you relied on this method please use getConfiguration() instead, but be aware that this is not an official API method. The recommended way to retrieve settings are injectSettings() methods (see manual for more information). Relates to #5577
[~TASK] FLOW3 (Configuration): Cleaned up and refactored the Configuration Manager's loadConfiguration() method. Resolves #5577
[BUGFIX] FLOW3 (Configuration): Fixed build of the caches configuration array. Resolves #5576.
Updated by Robert Lemke over 3 years ago
- Subject changed from Implement postprocessing and validation hooks into the configuration manager to Implement postprocessing and validation into the configuration manager
- Status changed from New to Accepted
- Target version set to 1.0 alpha 7
Realized that this will be difficult / impossible to implement because at the time the configuration is being parsed, most parts of FLOW3 (including Object Manager, AOP, Signal Slots etc.) have not yet been initialized.
However, the Configuration Manager could be refactored / cleaned up instead so it is more clear what each of the currently existing configuration types mean.