Larapie\Actions\Concerns\ResolvesAuthorization

Complexity

Total Complexity

6

Size/Duplication

Total Lines	28
Duplicated Lines	0 %

Test Coverage

Coverage

100%

Importance

Changes	1
Bugs	1	Features	0

4 Methods

Rating	Name	Duplication	Size	Complexity
A	passesAuthorization()	0	7	2
A	can()	0	3	1
A	failedAuthorization()	0	3	1
A	resolveAuthorization()	0	7	2

<?php

namespace Larapie\Actions\Concerns;

use Illuminate\Auth\Access\AuthorizationException;
use Illuminate\Support\Facades\Gate;

trait ResolvesAuthorization
{
    protected function resolveAuthorization()
    {
        if (! $this->passesAuthorization()) {
            $this->failedAuthorization();
        }

        return $this;
    }

    public function passesAuthorization()
    {
        if (method_exists($this, 'authorize')) {
            return $this->resolveAndCall($this, 'authorize');

It seems like resolveAndCall() must be provided by classes using this trait. How about adding it as abstract method to this trait?

        }

        return true;
    }

    protected function failedAuthorization()
    {
        throw new AuthorizationException('This action is unauthorized.');
    }

    protected function can($ability, $arguments = [])
    {
        return Gate::forUser($this->user())->allows($ability, $arguments);

It seems like user() must be provided by classes using this trait. How about adding it as abstract method to this trait?

    }
}