JsonData::getTargets() - Code Metrics - Inspection of "New archetype fields" - edmondscommerce/doctrine-static-meta - Measure and Improve Code Quality continuously with Scrutinizer

Passed

Pull Request — master (#170)

by Ross

created 2019-01-23 11:13 UTC

JsonData::getTargets() A

↳ Parent: JsonData

Complexity

Conditions	1
Paths	1

Size

Total Lines	3
Code Lines	1

Duplication

Lines	0
Ratio	0 %

Code Coverage

Tests	0
CRAP Score	2

Importance

Changes

Metric	Value
cc	1
eloc	1
nc	1
nop	0
dl	0
loc	3
ccs	0
cts	3
cp	0
crap	2
rs	10
c	0
b	0
f	0

<?php declare(strict_types=1);

namespace EdmondsCommerce\DoctrineStaticMeta\Entity\Validation\Constraints\FieldConstraints;

use Symfony\Component\Validator\Constraint;

/**
 * This is a template constraint. The Constraint does very little other than specify a message and imply a
 * ConstraintValidator with the same FQN as this class, but with `Validator` appended.
 *
 * @see https://symfony.com/doc/2.6/cookbook/validation/custom_constraint.html
 *
 * Suggest using the `./bin/doctrine dsm:override:create` command to create a new
 * override straight after you generate the file.
 *
 * Then you can edit it and update your override as required using
 * `./bin/doctrine dsm:overrides:update -a fromProject`
 *
 * And then reapply after a new build using
 * `./bin/doctrine dsm:overrides:update -a toProject`
 *
 */
class JsonData extends Constraint
{
    public const VALUE_TYPE = '(template value type)';

    public const MESSAGE = 'The value {{ string }} is not a valid JSON. Got the following error {{ error }} ' .
                           self::VALUE_TYPE;

    public $payload = self::MESSAGE;


    /**
     * Returns whether the constraint can be put onto classes, properties or
     * both.
     *
     * This method should return one or more of the constants
     * self::CLASS_CONSTRAINT and self::PROPERTY_CONSTRAINT.
     *
     * @return string One or more constant values
     */
    public function getTargets(): string
    {
        return self::PROPERTY_CONSTRAINT;
    }
}

1			<?php declare(strict_types=1);
2
3			namespace EdmondsCommerce\DoctrineStaticMeta\Entity\Validation\Constraints\FieldConstraints;
4
5			use Symfony\Component\Validator\Constraint;
6
7			/**
8			* This is a template constraint. The Constraint does very little other than specify a message and imply a
9			* ConstraintValidator with the same FQN as this class, but with `Validator` appended.
10			*
11			* @see https://symfony.com/doc/2.6/cookbook/validation/custom_constraint.html
12			*
13			* Suggest using the `./bin/doctrine dsm:override:create` command to create a new
14			* override straight after you generate the file.
15			*
16			* Then you can edit it and update your override as required using
17			* `./bin/doctrine dsm:overrides:update -a fromProject`
18			*
19			* And then reapply after a new build using
20			* `./bin/doctrine dsm:overrides:update -a toProject`
21			*
22			*/
23			class JsonData extends Constraint
24			{
25			public const VALUE_TYPE = '(template value type)';
26
27			public const MESSAGE = 'The value {{ string }} is not a valid JSON. Got the following error {{ error }} ' .
28			self::VALUE_TYPE;
29
30			public $payload = self::MESSAGE;
31
32
33			/**
34			* Returns whether the constraint can be put onto classes, properties or
35			* both.
36			*
37			* This method should return one or more of the constants
38			* self::CLASS_CONSTRAINT and self::PROPERTY_CONSTRAINT.
39			*
40			* @return string One or more constant values
41			*/
42			public function getTargets(): string
43			{
44			return self::PROPERTY_CONSTRAINT;
45			}
46			}

edmondscommerce / doctrine-static-meta

GitHub Access Token became invalid

Pull Request — master (#170)

JsonData::getTargets() A

Complexity

Size

Duplication

Code Coverage

Importance

Duplication Side-by-Side

Filter issues like