Arcanedev\LaravelAuth\Listeners\Users\GenerateConfirmationCode

Complexity

Total Complexity

2

Size/Duplication

Total Lines	21
Duplicated Lines	0 %

Coupling/Cohesion

Components	0
Dependencies	2

Test Coverage

Coverage

100%

Importance

Changes

0

1 Method

Rating	Name	Duplication	Size	Complexity
A	handle()	0	8	2

<?php namespace Arcanedev\LaravelAuth\Listeners\Users;

use Arcanedev\LaravelAuth\Events\Users\CreatingUser;
use Arcanedev\LaravelAuth\Services\UserConfirmator;

/**
 * Class     GenerateConfirmationCode
 *
 * @package  Arcanedev\LaravelAuth\Listeners\Users
 * @author   ARCANEDEV <arcanedev.maroc@gmail.com>
 */
class GenerateConfirmationCode
{
    /* -----------------------------------------------------------------
     |  Main Methods
     | -----------------------------------------------------------------
     */

    /**
     * Handle the event.
     *
     * @param  \Arcanedev\LaravelAuth\Events\Users\CreatingUser  $event
     */
    public function handle(CreatingUser $event)
    {
        if (UserConfirmator::isEnabled()) {
            $event->user->confirmation_code = UserConfirmator::generateCode();

Accessing confirmation_code on the interface Arcanesoft\Contracts\Auth\Models\User suggest that you code against a concrete implementation. How about adding an instanceof check?

        }

        return $event;
    }
}