SpecialMethods::__destruct() - Code Metrics - Inspection of "Convert the ClassMirror spec to an integration tes..." - phpspec/prophecy - Measure and Improve Code Quality continuously with Scrutinizer

Completed

Pull Request — master (#274)

by Christophe

created 2016-05-30 01:36 UTC

SpecialMethods::__destruct() A

↳ Parent: SpecialMethods

Complexity

Conditions	1
Paths	1

Size

Total Lines	3
Code Lines	1

Duplication

Lines	0
Ratio	0 %

Importance

Changes	1
Bugs	0	Features	0

Metric	Value
c	1
b	0
f	0
dl	0
loc	3
rs	10
cc	1
eloc	1
nc	1
nop	0

<?php

namespace Fixtures\Prophecy;

class SpecialMethods
{
    public function __construct()
    {
    }

    function __destruct()

    {
    }

    function __call($name, $arguments)

    {
    }

    function __sleep()

    {
    }

    function __wakeup()

    {
    }

    function __toString()

    {
        return '';
    }

    function __invoke()

    {
    }

}


1			<?php
2
3			namespace Fixtures\Prophecy;
4
5			class SpecialMethods
6			{
7			public function __construct()
8			{
9			}
10
11			function __destruct()
			0 ignored issues – show Best Practice introduced 2016-05-30 01:41 UTC by Report Bug Copy Issue Report It is generally recommended to explicitly declare the visibility for methods. Adding explicit visibility (`private`, `protected`, or `public`) is generally recommend to communicate to other developers how, and from where this method is intended to be used. Loading history...
12			{
13			}
14
15			function __call($name, $arguments)
			0 ignored issues – show Best Practice introduced 2016-05-30 01:41 UTC by Report Bug Copy Issue Report It is generally recommended to explicitly declare the visibility for methods. Adding explicit visibility (`private`, `protected`, or `public`) is generally recommend to communicate to other developers how, and from where this method is intended to be used. Loading history...
16			{
17			}
18
19			function __sleep()
			0 ignored issues – show Best Practice introduced 2016-05-30 01:41 UTC by Report Bug Copy Issue Report It is generally recommended to explicitly declare the visibility for methods. Adding explicit visibility (`private`, `protected`, or `public`) is generally recommend to communicate to other developers how, and from where this method is intended to be used. Loading history...
20			{
21			}
22
23			function __wakeup()
			0 ignored issues – show Best Practice introduced 2016-05-30 01:41 UTC by Report Bug Copy Issue Report It is generally recommended to explicitly declare the visibility for methods. Adding explicit visibility (`private`, `protected`, or `public`) is generally recommend to communicate to other developers how, and from where this method is intended to be used. Loading history...
24			{
25			}
26
27			function __toString()
			0 ignored issues – show Best Practice introduced 2016-05-30 01:41 UTC by Report Bug Copy Issue Report It is generally recommended to explicitly declare the visibility for methods. Adding explicit visibility (`private`, `protected`, or `public`) is generally recommend to communicate to other developers how, and from where this method is intended to be used. Loading history...
28			{
29			return '';
30			}
31
32			function __invoke()
			0 ignored issues – show Best Practice introduced 2016-05-30 01:41 UTC by Report Bug Copy Issue Report It is generally recommended to explicitly declare the visibility for methods. Adding explicit visibility (`private`, `protected`, or `public`) is generally recommend to communicate to other developers how, and from where this method is intended to be used. Loading history...
33			{
34			}
35
36			}
37

phpspec / prophecy

Pull Request — master (#274)

SpecialMethods::__destruct() A

Complexity

Size

Duplication

Importance

Duplication Side-by-Side

Filter issues like