Implement validation for settings (or configuration in general)
Currently settings, which are typically defined in .yaml files, won't be validated by FLOW3. It would, however, be quite convenient for a developer if he could rely on validated settings.
One way to implement this would be by introducing annotations for yaml comments. The developer would then define the expected datatype and additional validators in his Settings.yaml template file and these rules would be enforced while settings are appplied by the Configuration Manager.
Foo: /** * @type string * @validate StringLenth(minimum = "10") */ title: "The title of something"