No description
Find a file
2020-03-16 15:41:30 +01:00
Classes removed empty lines between @param and @return/@throws 2020-03-12 14:21:30 +01:00
Configuration/Testing add quotes around strings in YAML files 2018-04-03 17:53:57 +02:00
Migrations/Code optimize code migrations 2020-03-16 15:41:30 +01:00
Resources/Private/Schema write strings in yaml files in quotes 2020-03-11 10:39:33 +01:00
Tests/Functional PSR-12 for tests 2020-03-10 14:48:57 +01:00
.gitignore Initial commit 2014-04-18 14:20:28 +02:00
composer.json TASK: Apply migration Neos.Flow-20180415105700 2019-08-27 11:30:13 +02:00
License.txt Adding License and small readme 2015-04-29 17:50:13 +02:00
README.md removed trailing spaces 2020-03-11 12:09:37 +01:00

DigiComp.SettingValidator

This Package allows to configure Validators for your Action-Arguments or domain model properties to be set by a new Yaml-File in your Configuration directory.

Lets imagine you had this action-method:

/**
 * @param Order $order
 * @Flow\Validate(type="DigiComp.SettingValidator:Settings")
 */
public function createOrder($order) {...}

Then your Validation.yaml could look like this:

SuperVendor\SuperPackage\Domain\Model\Order:
  -
    property: price
    validator: NumberRange
    options:
      maximum: 20
      minimum: 10
  -
    validator: SuperVendor.SuperPackage:SomeOtherValidator #validates the complete object
    options: []
  -
    property: customer
    validator: DigiComp.SettingValidator:Settings
    options:
      name: OrderCustomer

OrderCustomer:
  -
    property: firstName
    validator: StringLength
    options:
      minimum: 3
      maximum: 20

As you see: Nesting is possible ;) That way you can easily construct flexible structures.

The SettingsValidator has an optional option: "name" - If you don't give one, it assumes your validation value is an object and searches in Validation.yaml for the FQCN.