ReplaceResult::for() - Code Metrics - Inspection of "Merge branch 'master' of github.com:spatie/regex" - spatie/regex - Measure and Improve Code Quality continuously with Scrutinizer

Completed

Push — master ( a0fab7...d931ca )

by Sebastian

created 2016-08-17 19:44 UTC

ReplaceResult::for() B

↳ Parent: ReplaceResult

Complexity

Conditions	4
Paths	7

Size

Total Lines	24
Code Lines	14

Duplication

Lines	0
Ratio	0 %

Importance

Changes

Metric	Value
dl	0
loc	24
rs	8.6845
c	0
b	0
f	0
cc	4
eloc	14
nc	7
nop	4

<?php

namespace Spatie\Regex;

class ReplaceResult extends RegexResult
{
    /** @var string|array */
    protected $pattern;

    /** @var string|array */
    protected $replacement;

    /** @var string|array */
    protected $subject;

    /** @var string|array */
    protected $result;

    /** @var int */
    protected $count;

    public function __construct($pattern, $replacement, $subject, $result, int $count)
    {
        $this->pattern = $pattern;
        $this->replacement = $replacement;
        $this->subject = $subject;
        $this->result = $result;
        $this->count = $count;
    }

    public static function for($pattern, $replacement, $subject, $limit)

    {
        $count = 0;

        try {
            if (is_callable($replacement)) {
class A {
    var $property;
}
                $replacement = function (array $matches) use ($pattern, $subject, $replacement) {
                    return $replacement(new MatchResult($pattern, $subject, true, $matches));
                };

                $result = preg_replace_callback($pattern, $replacement, $subject, $limit, $count);
class A {
    var $property;
}
            } else {
                $result = preg_replace($pattern, $replacement, $subject, $limit, $count);
class A {
    var $property;
}
            }
        } catch (Exception $exception) {
class A {
    var $property;
}
            throw RegexFailed::replace($pattern, $subject, $exception->getMessage());
        }

        if ($result === null) {
class A {
    var $property;
}
            throw RegexFailed::replace($pattern, $subject, static::lastPregError());
        }

        return new static($pattern, $replacement, $subject, $result, $count);
class A {
    var $property;
}
    }

    public function result()
    {
        return $this->result;
    }

    public function count()
    {
        return $this->count;
    }
}


1			<?php
2
3			namespace Spatie\Regex;
4
5			class ReplaceResult extends RegexResult
6			{
7			/** @var string\|array */
8			protected $pattern;
9
10			/** @var string\|array */
11			protected $replacement;
12
13			/** @var string\|array */
14			protected $subject;
15
16			/** @var string\|array */
17			protected $result;
18
19			/** @var int */
20			protected $count;
21
22			public function __construct($pattern, $replacement, $subject, $result, int $count)
23			{
24			$this->pattern = $pattern;
25			$this->replacement = $replacement;
26			$this->subject = $subject;
27			$this->result = $result;
28			$this->count = $count;
29			}
30
31			public static function for($pattern, $replacement, $subject, $limit)
			0 ignored issues – show Coding Style introduced 2016-08-17 19:46 UTC by Report Bug Copy Issue Report Possible parse error: non-abstract method defined as abstract Loading history... Coding Style introduced 2016-08-17 19:46 UTC by Report Bug Copy Issue Report It is generally advisable to only define one property per statement. Only declaring a single property per statement allows you to later on add doc comments more easily. It is also recommended by PSR2, so it is a common style that many people expect. Loading history...
32			{
33			$count = 0;
34
35			try {
36			if (is_callable($replacement)) {
			0 ignored issues – show Coding Style introduced 2016-08-17 19:46 UTC by Report Bug Copy Issue Report It is generally advisable to only define one property per statement. Only declaring a single property per statement allows you to later on add doc comments more easily. It is also recommended by PSR2, so it is a common style that many people expect. Loading history... Coding Style introduced 2016-08-17 19:46 UTC by Report Bug Copy Issue Report The visibility should be declared for property `$replacement`. The PSR-2 coding standard requires that all properties in a class have their visibility explicitly declared. If you declare a property using class A { var $property; } the property is implicitly global. To learn more about the PSR-2, please see the PHP-FIG site on the PSR-2. Loading history...
37			$replacement = function (array $matches) use ($pattern, $subject, $replacement) {
38			return $replacement(new MatchResult($pattern, $subject, true, $matches));
39			};
40
41			$result = preg_replace_callback($pattern, $replacement, $subject, $limit, $count);
			0 ignored issues – show Coding Style introduced 2016-08-17 19:46 UTC by Report Bug Copy Issue Report It is generally advisable to only define one property per statement. Only declaring a single property per statement allows you to later on add doc comments more easily. It is also recommended by PSR2, so it is a common style that many people expect. Loading history... Coding Style introduced 2016-08-17 19:46 UTC by Report Bug Copy Issue Report The visibility should be declared for property `$result`. The PSR-2 coding standard requires that all properties in a class have their visibility explicitly declared. If you declare a property using class A { var $property; } the property is implicitly global. To learn more about the PSR-2, please see the PHP-FIG site on the PSR-2. Loading history...
42			} else {
43			$result = preg_replace($pattern, $replacement, $subject, $limit, $count);
			0 ignored issues – show Coding Style introduced 2016-08-17 19:46 UTC by Report Bug Copy Issue Report It is generally advisable to only define one property per statement. Only declaring a single property per statement allows you to later on add doc comments more easily. It is also recommended by PSR2, so it is a common style that many people expect. Loading history... Coding Style introduced 2016-08-17 19:46 UTC by Report Bug Copy Issue Report The visibility should be declared for property `$result`. The PSR-2 coding standard requires that all properties in a class have their visibility explicitly declared. If you declare a property using class A { var $property; } the property is implicitly global. To learn more about the PSR-2, please see the PHP-FIG site on the PSR-2. Loading history...
44			}
45			} catch (Exception $exception) {
			0 ignored issues – show Bug introduced 2016-08-17 19:46 UTC by Report Bug Copy Issue Report The class `Spatie\Regex\Exception` does not exist. Did you forget a USE statement, or did you not list all dependencies? Scrutinizer analyzes your `composer.json`/`composer.lock` file if available to determine the classes, and functions that are defined by your dependencies. It seems like the listed class was neither found in your dependencies, nor was it found in the analyzed files in your repository. If you are using some other form of dependency management, you might want to disable this analysis. Loading history... Coding Style introduced 2016-08-17 19:46 UTC by Report Bug Copy Issue Report It is generally advisable to only define one property per statement. Only declaring a single property per statement allows you to later on add doc comments more easily. It is also recommended by PSR2, so it is a common style that many people expect. Loading history... Coding Style introduced 2016-08-17 19:46 UTC by Report Bug Copy Issue Report The visibility should be declared for property `$exception`. The PSR-2 coding standard requires that all properties in a class have their visibility explicitly declared. If you declare a property using class A { var $property; } the property is implicitly global. To learn more about the PSR-2, please see the PHP-FIG site on the PSR-2. Loading history...
46			throw RegexFailed::replace($pattern, $subject, $exception->getMessage());
47			}
48
49			if ($result === null) {
			0 ignored issues – show Coding Style introduced 2016-08-17 19:46 UTC by Report Bug Copy Issue Report It is generally advisable to only define one property per statement. Only declaring a single property per statement allows you to later on add doc comments more easily. It is also recommended by PSR2, so it is a common style that many people expect. Loading history... Coding Style introduced 2016-08-17 19:46 UTC by Report Bug Copy Issue Report The visibility should be declared for property `$result`. The PSR-2 coding standard requires that all properties in a class have their visibility explicitly declared. If you declare a property using class A { var $property; } the property is implicitly global. To learn more about the PSR-2, please see the PHP-FIG site on the PSR-2. Loading history...
50			throw RegexFailed::replace($pattern, $subject, static::lastPregError());
51			}
52
53			return new static($pattern, $replacement, $subject, $result, $count);
			0 ignored issues – show Coding Style introduced 2016-08-17 19:46 UTC by Report Bug Copy Issue Report It is generally advisable to only define one property per statement. Only declaring a single property per statement allows you to later on add doc comments more easily. It is also recommended by PSR2, so it is a common style that many people expect. Loading history... Coding Style introduced 2016-08-17 19:46 UTC by Report Bug Copy Issue Report The visibility should be declared for property `$pattern`. The PSR-2 coding standard requires that all properties in a class have their visibility explicitly declared. If you declare a property using class A { var $property; } the property is implicitly global. To learn more about the PSR-2, please see the PHP-FIG site on the PSR-2. Loading history...
54			}
55
56			public function result()
57			{
58			return $this->result;
59			}
60
61			public function count()
62			{
63			return $this->count;
64			}
65			}
66

spatie / regex

GitHub Access Token became invalid

Push — master ( a0fab7...d931ca )

ReplaceResult::for() B

Complexity

Size

Duplication

Importance

Duplication Side-by-Side

Filter issues like