ActivationEvent::__construct() - Code Metrics - Inspection of "Validate user repository service instance class in..." - fsi-open/admin-security-bundle - Measure and Improve Code Quality continuously with Scrutinizer

Completed

Pull Request — master (#91)

by Piotr

created 2017-05-09 12:32 UTC

ActivationEvent::__construct() A

↳ Parent: ActivationEvent

Complexity

Conditions	1
Paths	1

Size

Total Lines	4
Code Lines	2

Duplication

Lines	0
Ratio	0 %

Importance

Changes

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

<?php

/**
 * (c) FSi sp. z o.o. <[email protected]>
 *
 * For the full copyright and license information, please view the LICENSE
 * file that was distributed with this source code.
 */

namespace FSi\Bundle\AdminSecurityBundle\Event;

use FSi\Bundle\AdminSecurityBundle\Security\User\ActivableInterface;
use Symfony\Component\EventDispatcher\Event;

class ActivationEvent extends Event
{
    /**
     * @var ActivableInterface
     */
    private $user;

    /**
     * @param ActivableInterface $user
     */
    function __construct(ActivableInterface $user)

    {
        $this->user = $user;
    }

    /**
     * @return ActivableInterface
     */
    public function getUser()
    {
        return $this->user;
    }
}


1			<?php
2
3			/**
4			* (c) FSi sp. z o.o. <[email protected]>
5			*
6			* For the full copyright and license information, please view the LICENSE
7			* file that was distributed with this source code.
8			*/
9
10			namespace FSi\Bundle\AdminSecurityBundle\Event;
11
12			use FSi\Bundle\AdminSecurityBundle\Security\User\ActivableInterface;
13			use Symfony\Component\EventDispatcher\Event;
14
15			class ActivationEvent extends Event
16			{
17			/**
18			* @var ActivableInterface
19			*/
20			private $user;
21
22			/**
23			* @param ActivableInterface $user
24			*/
25			function __construct(ActivableInterface $user)
			0 ignored issues – show Best Practice introduced 2017-05-09 08:46 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...
26			{
27			$this->user = $user;
28			}
29
30			/**
31			* @return ActivableInterface
32			*/
33			public function getUser()
34			{
35			return $this->user;
36			}
37			}
38

fsi-open / admin-security-bundle

Pull Request — master (#91)

ActivationEvent::__construct() A

Complexity

Size

Duplication

Importance

Duplication Side-by-Side

Filter issues like