ModelHistoryTrait   A
last analyzed

Complexity

Total Complexity 2

Size/Duplication

Total Lines 17
Duplicated Lines 0 %

Coupling/Cohesion

Components 0
Dependencies 2

Importance

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

2 Methods

Rating   Name   Duplication   Size   Complexity  
A bootModelHistoryTrait() 0 6 1
A modelHistories() 0 4 1
1
<?php
2
3
namespace Hamidrezaniazi\Laramist\Traits;
4
5
use Hamidrezaniazi\Laramist\Models\ModelHistory;
6
use Illuminate\Database\Eloquent\Model;
7
use Illuminate\Database\Eloquent\Relations\MorphMany;
8
use Illuminate\Support\Facades\Auth;
9
10
trait ModelHistoryTrait
11
{
12
    public static function bootModelHistoryTrait()
13
    {
14
        static::updated(function (Model $model) {
15
            ModelHistory::logChanges($model, Auth::user());
16
        });
17
    }
18
19
    /**
20
     * @return MorphMany
21
     */
22
    public function modelHistories(): MorphMany
23
    {
24
        return $this->morphMany(ModelHistory::class, 'subject');
0 ignored issues
show
Bug introduced by
It seems like morphMany() 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...
25
    }
26
}
27