GitHub Access Token became invalid

It seems like the GitHub access token used for retrieving details about this repository from GitHub became invalid. This might prevent certain types of inspections from being run (in particular, everything related to pull requests).
Please ask an admin of your repository to re-new the access token on this website.

ControllerBehavior   A
last analyzed

Complexity

Total Complexity 1

Size/Duplication

Total Lines 7
Duplicated Lines 0 %

Coupling/Cohesion

Components 0
Dependencies 1
Metric Value
wmc 1
lcom 0
cbo 1
dl 0
loc 7
rs 10

1 Method

Rating   Name   Duplication   Size   Complexity  
A let() 0 4 1
1
<?php
2
/**
3
 * MageSpec
4
 *
5
 * NOTICE OF LICENSE
6
 *
7
 * This source file is subject to the MIT License, that is bundled with this
8
 * package in the file LICENSE.
9
 * It is also available through the world-wide-web at this URL:
10
 *
11
 * http://opensource.org/licenses/MIT
12
 *
13
 * If you did not receive a copy of the license and are unable to obtain it
14
 * through the world-wide-web, please send an email
15
 * to <[email protected]> so we can send you a copy immediately.
16
 *
17
 * @category   MageTest
18
 * @package    PhpSpec_MagentoExtension
19
 * @subpackage Specification
20
 *
21
 * @copyright  Copyright (c) 2012-2013 MageTest team and contributors.
22
 */
23
namespace MageTest\PhpSpec\MagentoExtension\Specification;
24
25
use PhpSpec\ObjectBehavior;
26
use Mage_Core_Controller_Request_Http as Request;
27
use Zend_Controller_Response_Abstract as Response;
28
29
/**
30
 * ControllerBehavior
31
 *
32
 * @category   MageTest
33
 * @package    PhpSpec_MagentoExtension
34
 * @subpackage Specification
35
 *
36
 * @author     MageTest team (https://github.com/MageTest/MageSpec/contributors)
37
 */
38
abstract class ControllerBehavior extends ObjectBehavior
39
{
40
    function let(Request $request, Response $response)
0 ignored issues
show
Best Practice introduced by
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...
Comprehensibility Best Practice introduced by
It is recommend to declare an explicit visibility for let.

Generally, we recommend to declare visibility for all methods in your source code. This has the advantage of clearly communication to other developers, and also yourself, how this method should be consumed.

If you are not sure which visibility to choose, it is a good idea to start with the most restrictive visibility, and then raise visibility as needed, i.e. start with private, and only raise it to protected if a sub-class needs to have access, or public if an external class needs access.

Loading history...
41
    {
42
        $this->beConstructedWith($request, $response);
43
    }
44
}
45