CanVerifyEmail - Code Metrics - rinvex/laravel-auth - Measure and Improve Code Quality continuously with Scrutinizer

CanVerifyEmail A
last analyzed 2021-02-28 06:07 UTC

↳ Parent: Project

Complexity

Total Complexity

Size/Duplication

Total Lines	27
Duplicated Lines	0 %

Coupling/Cohesion

Components	2
Dependencies	0

Importance

Changes

Metric	Value
dl	0
loc	27
c	0
b	0
f	0
rs	10
wmc	4
lcom	2
cbo	0

3 Methods

Rating	Name	Size	Complexity
A	getEmailForVerification()	4	1
A	sendEmailVerificationNotification()	5	2
A	hasVerifiedEmail()	4	1

<?php

declare(strict_types=1);

namespace Rinvex\Auth\Traits;

trait CanVerifyEmail
{
    /**
     * {@inheritdoc}
     */
    public function getEmailForVerification(): string
    {
        return $this->email;
class MyClass { }

$x = new MyClass();
$x->foo = true;
    }

    /**
     * {@inheritdoc}
     */
    public function hasVerifiedEmail(): bool
    {
        return ! is_null($this->email_verified_at);
class MyClass { }

$x = new MyClass();
$x->foo = true;
    }

    /**
     * {@inheritdoc}
     */
    public function sendEmailVerificationNotification(string $token, int $expiration): void
    {
        ! $this->emailVerificationNotificationClass
class MyClass { }

$x = new MyClass();
$x->foo = true;
        || $this->notify(new $this->emailVerificationNotificationClass($token, $expiration));
trait Idable {
    public function equalIds(Idable $other) {
        return $this->getId() === $other->getId();
    }
}
    }
}


1			<?php
2
3			declare(strict_types=1);
4
5			namespace Rinvex\Auth\Traits;
6
7			trait CanVerifyEmail
8			{
9			/**
10			* {@inheritdoc}
11			*/
12			public function getEmailForVerification(): string
13			{
14			return $this->email;
			0 ignored issues – show Bug introduced 2016-08-25 14:01 UTC by Report Bug Copy Issue Report The property `email` does not exist. Did you maybe forget to declare it? In PHP it is possible to write to properties without declaring them. For example, the following is perfectly valid PHP code: class MyClass { } $x = new MyClass(); $x->foo = true; Generally, it is a good practice to explictly declare properties to avoid accidental typos and provide IDE auto-completion: class MyClass { public $foo; } $x = new MyClass(); $x->foo = true; Loading history...
15			}
16
17			/**
18			* {@inheritdoc}
19			*/
20			public function hasVerifiedEmail(): bool
21			{
22			return ! is_null($this->email_verified_at);
			0 ignored issues – show Bug introduced 2018-12-20 21:09 UTC by Report Bug Copy Issue Report The property `email_verified_at` does not exist. Did you maybe forget to declare it? In PHP it is possible to write to properties without declaring them. For example, the following is perfectly valid PHP code: class MyClass { } $x = new MyClass(); $x->foo = true; Generally, it is a good practice to explictly declare properties to avoid accidental typos and provide IDE auto-completion: class MyClass { public $foo; } $x = new MyClass(); $x->foo = true; Loading history...
23			}
24
25			/**
26			* {@inheritdoc}
27			*/
28			public function sendEmailVerificationNotification(string $token, int $expiration): void
29			{
30			! $this->emailVerificationNotificationClass
			0 ignored issues – show Bug introduced 2018-01-31 14:20 UTC by Report Bug Copy Issue Report The property `emailVerificationNotificationClass` does not exist. Did you maybe forget to declare it? In PHP it is possible to write to properties without declaring them. For example, the following is perfectly valid PHP code: class MyClass { } $x = new MyClass(); $x->foo = true; Generally, it is a good practice to explictly declare properties to avoid accidental typos and provide IDE auto-completion: class MyClass { public $foo; } $x = new MyClass(); $x->foo = true; Loading history...
31			\|\| $this->notify(new $this->emailVerificationNotificationClass($token, $expiration));
			0 ignored issues – show Bug introduced 2018-01-31 14:20 UTC by Report Bug Copy Issue Report It seems like `notify()` must be provided by classes using this trait. How about adding it as abstract method to this trait? This check looks for methods that are used by a trait but not required by it. To illustrate, let’s look at the following code example trait Idable { public function equalIds(Idable $other) { return $this->getId() === $other->getId(); } } The trait `Idable` provides a method `equalsId` that in turn relies on the method `getId()`. If this method does not exist on a class mixing in this trait, the method will fail. Adding the `getId()` as an abstract method to the trait will make sure it is available. Loading history...
32			}
33			}
34

rinvex / laravel-auth

CanVerifyEmail A last analyzed 2021-02-28 06:07 UTC

Complexity

Size/Duplication

Coupling/Cohesion

Importance

3 Methods

Duplication Side-by-Side

Filter issues like

CanVerifyEmail A
last analyzed 2021-02-28 06:07 UTC