AbstractFormValidator::validateGhost() - Code Metrics - Inspection of "Merge branch 'development' into unit-tests-conditi..." - romm/formz - Measure and Improve Code Quality continuously with Scrutinizer

Completed

Push — unit-tests-conditions ( 15904b...8f07c8 )

by Romain

created 2017-03-07 12:53 UTC

AbstractFormValidator::validateGhost() A

↳ Parent: Project

Complexity

Conditions	2
Paths	2

Size

Total Lines	10
Code Lines	5

Duplication

Lines	0
Ratio	0 %

Importance

Changes

Metric	Value
dl	0
loc	10
rs	9.4285
c	0
b	0
f	0
cc	2
eloc	5
nc	2
nop	2

<?php
/*
 * 2017 Romain CANON <[email protected]>
 *
 * This file is part of the TYPO3 Formz project.
 * It is free software; you can redistribute it and/or modify it
 * under the terms of the GNU General Public License, either
 * version 3 of the License, or any later version.
 *
 * For the full copyright and license information, see:
 * http://www.gnu.org/licenses/gpl-3.0.html
 */

namespace Romm\Formz\Validation\Validator\Form;

use Romm\Formz\Configuration\Form\Field\Field;
use Romm\Formz\Core\Core;
use Romm\Formz\Error\FormResult;
use Romm\Formz\Exceptions\InvalidArgumentTypeException;
use Romm\Formz\Form\FormInterface;
use Romm\Formz\Service\FormService;
use TYPO3\CMS\Extbase\Validation\Validator\AbstractValidator as ExtbaseAbstractValidator;

/**
 * This is the abstract form validator, which must be inherited by any custom
 * form validator in order to work properly.
 *
 * Please note that a default form validator already exists if you need a form
 * which does not require any particular action: `DefaultFormValidator`.
 *
 * A form validator should be called to validate any form instance (which is a
 * child of `AbstractForm`). Usually, this is used in controller actions to
 * validate a form sent by the user. Example:
 *
 * /**
 *  * Action called when the Example form is submitted.
 *  *
 *  * @param $exForm
 *  * @validate $exForm Romm.Formz:Form\DefaultFormValidator
 *  * /
 *  public function submitFormAction(ExampleForm $exForm) { ... }
 *
 *******************************************************************************
 *
 * You may use you own custom form validator in order to be able to use the
 * following features:
 *
 * - Pre-validation custom process:
 *   By extending the method `beforeValidationProcess()`, you are able to handle
 *   anything you want just before the form validation begins to loop on every
 *   field. This can be used for instance to (de)activate the validation of
 *   certain fields under very specific circumstances.
 *
 * - In real time custom process:
 *   After each field went trough a validation process, a magic method is called
 *   to allow very low level custom process. The magic method name looks like:
 *   "{lowerCamelCaseFieldName}Validated". For instance, when the "email" field
 *   just went trough the validation process, the method `emailValidated()` is
 *   called.
 *
 * - Post-validation custom process:
 *   After the validation was done on every field of the form, this method is
 *   called to allow you high level process. For instance, let's assume your
 *   form is used to calculate a price estimation depending on information
 *   submitted in the form; when the form went trough the validation process and
 *   got no error, you can run the price estimation, and if any error occurs you
 *   are still able to add an error to `$this->result` (in a controller you do
 *   not have access to it anymore).
 */
abstract class AbstractFormValidator extends ExtbaseAbstractValidator implements FormValidatorInterface
{
    /**
     * @inheritdoc
     */
    protected $supportedOptions = [
        'name' => ['', 'Name of the form.', 'string', true]
    ];

    /**
     * @var FormResult
     */
    protected $result;

    /**
     * @var FormValidatorExecutor
     */
    protected $formValidatorExecutor;

    protected function initializeValidator($form)
    {
        if (false === $form instanceof FormInterface) {
            throw InvalidArgumentTypeException::validatingWrongFormType(get_class($form));
        }

        $this->result = new FormResult;
        $this->formValidatorExecutor = $this->getFormValidatorExecutor($form);
    }

    /**
     * Checks the given form instance, and launches the validation if it is a
     * correct form.
     *
     * @param FormInterface $form The form instance to be validated.
     * @return FormResult
     */
    final public function validate($form)
    {
        $this->initializeValidator($form);

        $formObject = $this->formValidatorExecutor->getFormObject();
        $formObject->markFormAsSubmitted();
        $formObject->setForm($form);

        $this->validateGhost($form, false);

        $formObject->setFormResult($this->result);

        return $this->result;
    }

    /**
     * Validates the form, but wont save form data in the form object.
     *
     * @param FormInterface $form
     * @param bool          $initialize
     * @return FormResult
     */
    public function validateGhost($form, $initialize = true)
    {
        if ($initialize) {
            $this->initializeValidator($form);
        }

        $this->isValid($form);

        return $this->result;
    }

    /**
     * Runs the whole validation workflow.
     *
     * @param FormInterface $form
     */
    final public function isValid($form)
    {
        $this->formValidatorExecutor->applyBehaviours();
        $this->formValidatorExecutor->checkFieldsActivation();

        $this->beforeValidationProcess();

        $this->formValidatorExecutor->validateFields(function (Field $field) {
            $this->callAfterFieldValidationMethod($field);
        });

        $this->afterValidationProcess();

        if ($this->result->hasErrors()) {
            // Storing the form for possible third party further usage.
            FormService::addFormWithErrors($form);
        }
    }

    /**
     * Use this function to (de)activate the validation for some given fields.
     */
    protected function beforeValidationProcess()
    {
    }

    /**
     * Use this function to run your own processes after the validation ran.
     */
    protected function afterValidationProcess()
    {
    }

    /**
     * After each field has been validated, a matching method can be called if
     * it exists in the child class.
     *
     * The syntax is `{lowerCamelCaseFieldName}Validated()`.
     *
     * Example: for field `firstName` - `firstNameValidated()`.
     *
     * @param Field $field
     */
    private function callAfterFieldValidationMethod(Field $field)
    {
        $functionName = lcfirst($field->getFieldName() . 'Validated');

        if (method_exists($this, $functionName)) {
            call_user_func([$this, $functionName]);
        }
    }

    /**
     * @param FormInterface $form
     * @return FormValidatorExecutor
     */
    protected function getFormValidatorExecutor(FormInterface $form)
    {
        /** @var FormValidatorExecutor $formValidatorExecutor */
        $formValidatorExecutor = Core::instantiate(FormValidatorExecutor::class, $form, $this->options['name'], $this->result);

        return $formValidatorExecutor;
    }
}


1			<?php
2			/*
3			* 2017 Romain CANON <[email protected]>
4			*
5			* This file is part of the TYPO3 Formz project.
6			* It is free software; you can redistribute it and/or modify it
7			* under the terms of the GNU General Public License, either
8			* version 3 of the License, or any later version.
9			*
10			* For the full copyright and license information, see:
11			* http://www.gnu.org/licenses/gpl-3.0.html
12			*/
13
14			namespace Romm\Formz\Validation\Validator\Form;
15
16			use Romm\Formz\Configuration\Form\Field\Field;
17			use Romm\Formz\Core\Core;
18			use Romm\Formz\Error\FormResult;
19			use Romm\Formz\Exceptions\InvalidArgumentTypeException;
20			use Romm\Formz\Form\FormInterface;
21			use Romm\Formz\Service\FormService;
22			use TYPO3\CMS\Extbase\Validation\Validator\AbstractValidator as ExtbaseAbstractValidator;
23
24			/**
25			* This is the abstract form validator, which must be inherited by any custom
26			* form validator in order to work properly.
27			*
28			* Please note that a default form validator already exists if you need a form
29			* which does not require any particular action: `DefaultFormValidator`.
30			*
31			* A form validator should be called to validate any form instance (which is a
32			* child of `AbstractForm`). Usually, this is used in controller actions to
33			* validate a form sent by the user. Example:
34			*
35			* /**
36			* * Action called when the Example form is submitted.
37			* *
38			* * @param $exForm
39			* * @validate $exForm Romm.Formz:Form\DefaultFormValidator
40			* * /
41			* public function submitFormAction(ExampleForm $exForm) { ... }
42			*
43			*******************************************************************************
44			*
45			* You may use you own custom form validator in order to be able to use the
46			* following features:
47			*
48			* - Pre-validation custom process:
49			* By extending the method `beforeValidationProcess()`, you are able to handle
50			* anything you want just before the form validation begins to loop on every
51			* field. This can be used for instance to (de)activate the validation of
52			* certain fields under very specific circumstances.
53			*
54			* - In real time custom process:
55			* After each field went trough a validation process, a magic method is called
56			* to allow very low level custom process. The magic method name looks like:
57			* "{lowerCamelCaseFieldName}Validated". For instance, when the "email" field
58			* just went trough the validation process, the method `emailValidated()` is
59			* called.
60			*
61			* - Post-validation custom process:
62			* After the validation was done on every field of the form, this method is
63			* called to allow you high level process. For instance, let's assume your
64			* form is used to calculate a price estimation depending on information
65			* submitted in the form; when the form went trough the validation process and
66			* got no error, you can run the price estimation, and if any error occurs you
67			* are still able to add an error to `$this->result` (in a controller you do
68			* not have access to it anymore).
69			*/
70			abstract class AbstractFormValidator extends ExtbaseAbstractValidator implements FormValidatorInterface
71			{
72			/**
73			* @inheritdoc
74			*/
75			protected $supportedOptions = [
76			'name' => ['', 'Name of the form.', 'string', true]
77			];
78
79			/**
80			* @var FormResult
81			*/
82			protected $result;
83
84			/**
85			* @var FormValidatorExecutor
86			*/
87			protected $formValidatorExecutor;
88
89			protected function initializeValidator($form)
90			{
91			if (false === $form instanceof FormInterface) {
92			throw InvalidArgumentTypeException::validatingWrongFormType(get_class($form));
93			}
94
95			$this->result = new FormResult;
96			$this->formValidatorExecutor = $this->getFormValidatorExecutor($form);
97			}
98
99			/**
100			* Checks the given form instance, and launches the validation if it is a
101			* correct form.
102			*
103			* @param FormInterface $form The form instance to be validated.
104			* @return FormResult
105			*/
106			final public function validate($form)
107			{
108			$this->initializeValidator($form);
109
110			$formObject = $this->formValidatorExecutor->getFormObject();
111			$formObject->markFormAsSubmitted();
112			$formObject->setForm($form);
113
114			$this->validateGhost($form, false);
115
116			$formObject->setFormResult($this->result);
117
118			return $this->result;
119			}
120
121			/**
122			* Validates the form, but wont save form data in the form object.
123			*
124			* @param FormInterface $form
125			* @param bool $initialize
126			* @return FormResult
127			*/
128			public function validateGhost($form, $initialize = true)
129			{
130			if ($initialize) {
131			$this->initializeValidator($form);
132			}
133
134			$this->isValid($form);
135
136			return $this->result;
137			}
138
139			/**
140			* Runs the whole validation workflow.
141			*
142			* @param FormInterface $form
143			*/
144			final public function isValid($form)
145			{
146			$this->formValidatorExecutor->applyBehaviours();
147			$this->formValidatorExecutor->checkFieldsActivation();
148
149			$this->beforeValidationProcess();
150
151			$this->formValidatorExecutor->validateFields(function (Field $field) {
152			$this->callAfterFieldValidationMethod($field);
153			});
154
155			$this->afterValidationProcess();
156
157			if ($this->result->hasErrors()) {
158			// Storing the form for possible third party further usage.
159			FormService::addFormWithErrors($form);
160			}
161			}
162
163			/**
164			* Use this function to (de)activate the validation for some given fields.
165			*/
166			protected function beforeValidationProcess()
167			{
168			}
169
170			/**
171			* Use this function to run your own processes after the validation ran.
172			*/
173			protected function afterValidationProcess()
174			{
175			}
176
177			/**
178			* After each field has been validated, a matching method can be called if
179			* it exists in the child class.
180			*
181			* The syntax is `{lowerCamelCaseFieldName}Validated()`.
182			*
183			* Example: for field `firstName` - `firstNameValidated()`.
184			*
185			* @param Field $field
186			*/
187			private function callAfterFieldValidationMethod(Field $field)
188			{
189			$functionName = lcfirst($field->getFieldName() . 'Validated');
190
191			if (method_exists($this, $functionName)) {
192			call_user_func([$this, $functionName]);
193			}
194			}
195
196			/**
197			* @param FormInterface $form
198			* @return FormValidatorExecutor
199			*/
200			protected function getFormValidatorExecutor(FormInterface $form)
201			{
202			/** @var FormValidatorExecutor $formValidatorExecutor */
203			$formValidatorExecutor = Core::instantiate(FormValidatorExecutor::class, $form, $this->options['name'], $this->result);
204
205			return $formValidatorExecutor;
206			}
207			}
208

romm / formz

Push — unit-tests-conditions ( 15904b...8f07c8 )

AbstractFormValidator::validateGhost() A

Complexity

Size

Duplication

Importance

Duplication Side-by-Side

Filter issues like