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.
Completed
Push — master ( b97e0a...a0b329 )
by Pascal
01:16
created

VerifyFirstEmail   A

Complexity

Total Complexity 2

Size/Duplication

Total Lines 31
Duplicated Lines 100 %

Coupling/Cohesion

Components 0
Dependencies 4

Importance

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

2 Methods

Rating   Name   Duplication   Size   Complexity  
A __construct() 4 4 1
A build() 6 6 1

How to fix   Duplicated Code   

Duplicated Code

Duplicate code is one of the most pungent code smells. A rule that is often used is to re-structure code once it is duplicated in three or more places.

Common duplication problems, and corresponding solutions are:

1
<?php
2
3
namespace ProtoneMedia\LaravelVerifyNewEmail\Mail;
4
5
use Illuminate\Bus\Queueable;
6
use Illuminate\Contracts\Queue\ShouldQueue;
7
use Illuminate\Mail\Mailable;
8
use Illuminate\Queue\SerializesModels;
9
use ProtoneMedia\LaravelVerifyNewEmail\PendingUserEmail;
10
11 View Code Duplication
class VerifyFirstEmail extends Mailable implements ShouldQueue
0 ignored issues
show
Duplication introduced by
This class seems to be duplicated in your project.

Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation.

You can also find more detailed suggestions in the “Code” section of your repository.

Loading history...
12
{
13
    use Queueable, SerializesModels;
14
15
    /**
16
     * @var \ProtoneMedia\LaravelVerifyNewEmail\PendingUserEmail
17
     */
18
    public $pendingUserEmail;
19
20
    /**
21
     * Create a new message instance.
22
     *
23
     * @return void
0 ignored issues
show
Comprehensibility Best Practice introduced by
Adding a @return annotation to constructors is generally not recommended as a constructor does not have a meaningful return value.

Adding a @return annotation to a constructor is not recommended, since a constructor does not have a meaningful return value.

Please refer to the PHP core documentation on constructors.

Loading history...
24
     */
25
    public function __construct(PendingUserEmail $pendingUserEmail)
26
    {
27
        $this->pendingUserEmail = $pendingUserEmail;
28
    }
29
30
    /**
31
     * Build the message.
32
     *
33
     * @return $this
34
     */
35
    public function build()
36
    {
37
        return $this->markdown('verify-new-email::verifyNewEmail', [
38
            'url' => $this->pendingUserEmail->verificationUrl(),
39
        ]);
40
    }
41
}
42