Completed
Pull Request — master (#627)
by Tom
02:12
created

DetectsChanges::attributesToBeLogged()   B

Complexity

Conditions 9
Paths 24

Size

Total Lines 26

Duplication

Lines 0
Ratio 0 %

Code Coverage

Tests 13
CRAP Score 9

Importance

Changes 0
Metric Value
cc 9
nc 24
nop 0
dl 0
loc 26
ccs 13
cts 13
cp 1
crap 9
rs 8.0555
c 0
b 0
f 0
1
<?php
2
3
namespace Spatie\Activitylog\Traits;
4
5
use Illuminate\Contracts\Support\Arrayable;
6
use Illuminate\Support\Arr;
7
use Illuminate\Support\Str;
8
use Illuminate\Database\Eloquent\Model;
9
use Spatie\Activitylog\Exceptions\CouldNotLogChanges;
10
11
trait DetectsChanges
12
{
13
    protected $oldAttributes = [];
14
15 224
    protected static function bootDetectsChanges()
16
    {
17 224
        if (static::eventsToBeRecorded()->contains('updated')) {
18
            static::updating(function (Model $model) {
19
20
                //temporary hold the original attributes on the model
21
                //as we'll need these in the updating event
22 112
                $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...
23
24 112
                $model->oldAttributes = static::logChanges($oldValues);
25 224
            });
26
        }
27 224
    }
28
29 216
    public function attributesToBeLogged(): array
30
    {
31 216
        $attributes = [];
32
33 216
        if (isset(static::$logFillable) && static::$logFillable) {
34 8
            $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...
35
        }
36
37 216
        if ($this->shouldLogUnguarded()) {
38 4
            $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...
39
        }
40
41 216
        if (isset(static::$logAttributes) && is_array(static::$logAttributes)) {
42 144
            $attributes = array_merge($attributes, array_diff(static::$logAttributes, ['*']));
43
44 144
            if (in_array('*', static::$logAttributes)) {
45 40
                $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...
46
            }
47
        }
48
49 216
        if (isset(static::$logAttributesToIgnore) && is_array(static::$logAttributesToIgnore)) {
50 8
            $attributes = array_diff($attributes, static::$logAttributesToIgnore);
51
        }
52
53 216
        return $attributes;
54
    }
55
56 148
    public function shouldLogOnlyDirty(): bool
57
    {
58 148
        if (! isset(static::$logOnlyDirty)) {
59 88
            return false;
60
        }
61
62 60
        return static::$logOnlyDirty;
63
    }
64
65 216
    public function shouldLogUnguarded(): bool
66
    {
67 216
        if (! isset(static::$logUnguarded)) {
68 208
            return false;
69
        }
70
71 8
        if (! static::$logUnguarded) {
72
            return false;
73
        }
74
75 8
        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...
76 4
            return false;
77
        }
78
79 4
        return true;
80
    }
81
82 216
    public function attributeValuesToBeLogged(string $processingEvent): array
83
    {
84 216
        if (! count($this->attributesToBeLogged())) {
85 68
            return [];
86
        }
87
88 148
        $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...
89 148
            $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...
90 148
                ? $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...
91 148
                : $this
92
        );
93
94 148
        if (static::eventsToBeRecorded()->contains('updated') && $processingEvent == 'updated') {
95 88
            $nullProperties = array_fill_keys(array_keys($properties['attributes']), null);
96
97 88
            $properties['old'] = array_merge($nullProperties, $this->oldAttributes);
98
99 88
            $this->oldAttributes = [];
100
        }
101
102 148
        if ($this->shouldLogOnlyDirty() && isset($properties['old'])) {
103 56
            $properties['attributes'] = array_udiff_assoc(
104 56
                $properties['attributes'],
105 56
                $properties['old'],
106
                function ($new, $old) {
107 56
                    if ($old === null || $new === null) {
108 20
                        return $new === $old ? 0 : 1;
109
                    }
110
111 52
                    return $new <=> $old;
112 56
                }
113
            );
114 56
            $properties['old'] = collect($properties['old'])
115 56
                ->only(array_keys($properties['attributes']))
116 56
                ->all();
117
        }
118
119 148
        return $properties;
120
    }
121
122 172
    public static function logChanges(Model $model): array
123
    {
124 172
        $changes = [];
125 172
        $attributes = $model->attributesToBeLogged();
126
127 172
        foreach ($attributes as $attribute) {
128 148
            if (Str::contains($attribute, '.')) {
129 24
                $changes += self::getRelatedModelAttributeValue($model, $attribute);
130
131 24
                continue;
132
            }
133
134 148
            if (Str::contains($attribute, '->')) {
135 24
                Arr::set(
136 24
                    $changes,
137 24
                    str_replace('->', '.', $attribute),
138 24
                    static::getModelAttributeJsonValue($model, $attribute)
139
                );
140
141 24
                continue;
142
            }
143
144 148
            $changes[$attribute] = $model->getAttribute($attribute);
145
146 148
            if (is_null($changes[$attribute])) {
147 72
                continue;
148
            }
149
150 148
            if ($model->isDateAttribute($attribute)) {
0 ignored issues
show
Bug introduced by
The method isDateAttribute() 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...
151 40
                $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...
152 40
                    $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...
153
                );
154
            }
155
156 148
            if ($model->hasCast($attribute)) {
157 48
                $cast = $model->getCasts()[$attribute];
158
159 48
                if ($model->isCustomDateTimeCast($cast)) {
0 ignored issues
show
Bug introduced by
The method isCustomDateTimeCast() 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...
160 4
                    $changes[$attribute] = $model->asDateTime($changes[$attribute])->format(explode(':', $cast, 2)[1]);
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...
161
                }
162
            }
163
        }
164
165 172
        return $changes;
166
    }
167
168 24
    protected static function getRelatedModelAttributeValue(Model $model, string $attribute): array
169
    {
170 24
        if (substr_count($attribute, '.') > 1) {
171
            throw CouldNotLogChanges::invalidAttribute($attribute);
172
        }
173
174 24
        [$relatedModelName, $relatedAttribute] = explode('.', $attribute);
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...
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...
175
176 24
        $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...
177
178 24
        $relatedModel = $model->$relatedModelName ?? $model->$relatedModelName();
179
180 24
        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...
181
    }
182
183 24
    protected static function getModelAttributeJsonValue(Model $model, string $attribute)
184
    {
185 24
        $path = explode('->', $attribute);
186 24
        $modelAttribute = array_shift($path);
187 24
        $modelAttribute = collect($model->getAttribute($modelAttribute));
188
189 24
        return data_get($modelAttribute, implode('.', $path));
190
    }
191
}
192