Feature #5068
Implement validation for settings (or configuration in general)
Status: | Resolved | Start date: | 2009-10-21 | |
---|---|---|---|---|
Priority: | Should have | Due date: | ||
Assigned To: | - | % Done: | 0% |
|
Category: | Configuration | |||
Target version: | - | |||
PHP Version: | Complexity: | |||
Has patch: |
Description
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.
Example:
Foo: /** * @type string * @validate StringLenth(minimum = "10") */ title: "The title of something"
Related issues
History
#1 Updated by Martin Ficzel about 3 years ago
- Status changed from New to Resolved
Applied in changeset 1c8a80de60bff7ad0f878ade7e1cedc0f28ee365.