Completed
Push — master ( a63f6c...a28239 )
by Tom
13:33 queued 07:10
created

DetectsChanges::logChanges()   B

Complexity

Conditions 6
Paths 5

Size

Total Lines 30

Duplication

Lines 0
Ratio 0 %

Code Coverage

Tests 13
CRAP Score 6.0131

Importance

Changes 0
Metric Value
cc 6
nc 5
nop 1
dl 0
loc 30
ccs 13
cts 14
cp 0.9286
crap 6.0131
rs 8.8177
c 0
b 0
f 0
1
<?php
2
3
namespace Spatie\Activitylog\Traits;
4
5
use Illuminate\Support\Arr;
6
use Illuminate\Support\Str;
7
use Illuminate\Database\Eloquent\Model;
8
use Spatie\Activitylog\Exceptions\CouldNotLogChanges;
9
10
trait DetectsChanges
11
{
12
    protected $oldAttributes = [];
13 192
14
    protected static function bootDetectsChanges()
15 192
    {
16
        if (static::eventsToBeRecorded()->contains('updated')) {
17
            static::updating(function (Model $model) {
18
19
                //temporary hold the original attributes on the model
20 92
                //as we'll need these in the updating event
21
                $oldValues = (new static)->setRawAttributes($model->getOriginal());
0 ignored issues
show
Bug introduced by
It seems like setRawAttributes() 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...
22 92
23 192
                $model->oldAttributes = static::logChanges($oldValues);
24
            });
25 192
        }
26
    }
27 184
28
    public function attributesToBeLogged(): array
29 184
    {
30
        $attributes = [];
31 184
32 8
        if (isset(static::$logFillable) && static::$logFillable) {
33
            $attributes = array_merge($attributes, $this->getFillable());
0 ignored issues
show
Bug introduced by
It seems like getFillable() 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...
34
        }
35 184
36 4
        if ($this->shouldLogUnguarded()) {
37
            $attributes = array_merge($attributes, array_diff(array_keys($this->getAttributes()), $this->getGuarded()));
0 ignored issues
show
Bug introduced by
It seems like getAttributes() 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...
Bug introduced by
It seems like getGuarded() 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...
38
        }
39 184
40 112
        if (isset(static::$logAttributes) && is_array(static::$logAttributes)) {
41
            $attributes = array_merge($attributes, array_diff(static::$logAttributes, ['*']));
42 112
43 32
            if (in_array('*', static::$logAttributes)) {
44
                $attributes = array_merge($attributes, array_keys($this->getAttributes()));
0 ignored issues
show
Bug introduced by
It seems like getAttributes() 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...
45
            }
46
        }
47 184
48 8
        if (isset(static::$logAttributesToIgnore) && is_array(static::$logAttributesToIgnore)) {
49
            $attributes = array_diff($attributes, static::$logAttributesToIgnore);
50
        }
51 184
52
        return $attributes;
53
    }
54 116
55
    public function shouldLogOnlyDirty(): bool
56 116
    {
57 80
        if (! isset(static::$logOnlyDirty)) {
58
            return false;
59
        }
60 36
61
        return static::$logOnlyDirty;
62
    }
63 184
64
    public function shouldLogUnguarded(): bool
65 184
    {
66 176
        if (! isset(static::$logUnguarded)) {
67
            return false;
68
        }
69 8
70
        if (! static::$logUnguarded) {
71
            return false;
72
        }
73 8
74 4
        if (in_array('*', $this->getGuarded())) {
0 ignored issues
show
Bug introduced by
It seems like getGuarded() 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...
75
            return false;
76
        }
77 4
78
        return true;
79
    }
80 184
81
    public function attributeValuesToBeLogged(string $processingEvent): array
82 184
    {
83 68
        if (! count($this->attributesToBeLogged())) {
84
            return [];
85
        }
86 116
87 116
        $properties['attributes'] = static::logChanges(
0 ignored issues
show
Coding Style Comprehensibility introduced by
$properties was never initialized. Although not strictly required by PHP, it is generally a good practice to add $properties = array(); before regardless.

Adding an explicit array definition is generally preferable to implicit array definition as it guarantees a stable state of the code.

Let’s take a look at an example:

foreach ($collection as $item) {
    $myArray['foo'] = $item->getFoo();

    if ($item->hasBar()) {
        $myArray['bar'] = $item->getBar();
    }

    // do something with $myArray
}

As you can see in this example, the array $myArray is initialized the first time when the foreach loop is entered. You can also see that the value of the bar key is only written conditionally; thus, its value might result from a previous iteration.

This might or might not be intended. To make your intention clear, your code more readible and to avoid accidental bugs, we recommend to add an explicit initialization $myArray = array() either outside or inside the foreach loop.

Loading history...
88 116
            $this->exists
0 ignored issues
show
Bug introduced by
The property exists 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...
89 116
                ? $this->fresh() ?? $this
0 ignored issues
show
Bug introduced by
It seems like fresh() 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...
90
                : $this
91
        );
92 116
93 68
        if (static::eventsToBeRecorded()->contains('updated') && $processingEvent == 'updated') {
94
            $nullProperties = array_fill_keys(array_keys($properties['attributes']), null);
95 68
96
            $properties['old'] = array_merge($nullProperties, $this->oldAttributes);
97 68
98
            $this->oldAttributes = [];
99
        }
100 116
101 36
        if ($this->shouldLogOnlyDirty() && isset($properties['old'])) {
102 36
            $properties['attributes'] = array_udiff_assoc(
103 36
                $properties['attributes'],
104
                $properties['old'],
105 36
                function ($new, $old) {
106 20
                    if ($old === null || $new === null) {
107
                        return $new === $old ? 0 : 1;
108
                    }
109 32
110 36
                    return $new <=> $old;
111
                }
112 36
            );
113 36
            $properties['old'] = collect($properties['old'])
114 36
                ->only(array_keys($properties['attributes']))
115
                ->all();
116
        }
117 116
118
        return $properties;
119
    }
120 140
121
    public static function logChanges(Model $model): array
122 140
    {
123 140
        $changes = [];
124
        $attributes = $model->attributesToBeLogged();
125 140
126 116
        foreach ($attributes as $attribute) {
127 24
            if (Str::contains($attribute, '.')) {
128
                $changes += self::getRelatedModelAttributeValue($model, $attribute);
129 116
            } elseif (Str::contains($attribute, '->')) {
130
                Arr::set(
131
                    $changes,
132 116
                    str_replace('->', '.', $attribute),
133 116
                    static::getModelAttributeJsonValue($model, $attribute)
134
                );
135 32
            } else {
136 32
                $changes[$attribute] = $model->getAttribute($attribute);
137
138
                if (
139
                    in_array($attribute, $model->getDates())
140
                    && ! is_null($changes[$attribute])
141
                ) {
142 140
                    $changes[$attribute] = $model->serializeDate(
0 ignored issues
show
Bug introduced by
The method serializeDate() cannot be called from this context as it is declared protected in class Illuminate\Database\Eloq...\Concerns\HasAttributes.

This check looks for access to methods that are not accessible from the current context.

If you need to make a method accessible to another context you can raise its visibility level in the defining class.

Loading history...
143
                        $model->asDateTime($changes[$attribute])
0 ignored issues
show
Bug introduced by
The method asDateTime() cannot be called from this context as it is declared protected in class Illuminate\Database\Eloq...\Concerns\HasAttributes.

This check looks for access to methods that are not accessible from the current context.

If you need to make a method accessible to another context you can raise its visibility level in the defining class.

Loading history...
144
                    );
145 24
                }
146
            }
147 24
        }
148
149
        return $changes;
150
    }
151 24
152
    protected static function getRelatedModelAttributeValue(Model $model, string $attribute): array
153 24
    {
154
        if (substr_count($attribute, '.') > 1) {
155 24
            throw CouldNotLogChanges::invalidAttribute($attribute);
156
        }
157 24
158
        [$relatedModelName, $relatedAttribute] = explode('.', $attribute);
0 ignored issues
show
Bug introduced by
The variable $relatedAttribute does not exist. Did you mean $attribute?

This check looks for variables that are accessed but have not been defined. It raises an issue if it finds another variable that has a similar name.

The variable may have been renamed without also renaming all references.

Loading history...
Bug introduced by
The variable $relatedModelName seems only to be defined at a later point. Did you maybe move this code here without moving the variable definition?

This error can happen if you refactor code and forget to move the variable initialization.

Let’s take a look at a simple example:

function someFunction() {
    $x = 5;
    echo $x;
}

The above code is perfectly fine. Now imagine that we re-order the statements:

function someFunction() {
    echo $x;
    $x = 5;
}

In that case, $x would be read before it is initialized. This was a very basic example, however the principle is the same for the found issue.

Loading history...
159
160
        $relatedModelName = Str::camel($relatedModelName);
0 ignored issues
show
Bug introduced by
The variable $relatedModelName seems only to be defined at a later point. Did you maybe move this code here without moving the variable definition?

This error can happen if you refactor code and forget to move the variable initialization.

Let’s take a look at a simple example:

function someFunction() {
    $x = 5;
    echo $x;
}

The above code is perfectly fine. Now imagine that we re-order the statements:

function someFunction() {
    echo $x;
    $x = 5;
}

In that case, $x would be read before it is initialized. This was a very basic example, however the principle is the same for the found issue.

Loading history...
161
162
        $relatedModel = $model->$relatedModelName ?? $model->$relatedModelName();
163
164
        return ["{$relatedModelName}.{$relatedAttribute}" => $relatedModel->$relatedAttribute ?? null];
0 ignored issues
show
Bug introduced by
The variable $relatedAttribute does not exist. Did you mean $attribute?

This check looks for variables that are accessed but have not been defined. It raises an issue if it finds another variable that has a similar name.

The variable may have been renamed without also renaming all references.

Loading history...
165
    }
166
167
    protected static function getModelAttributeJsonValue(Model $model, string $attribute)
168
    {
169
        $path = explode('->', $attribute);
170
        $modelAttribute = array_shift($path);
171
        $modelAttribute = collect($model->getAttribute($modelAttribute));
172
173
        return data_get($modelAttribute, implode('.', $path));
174
    }
175
}
176