Scrutinizer GitHub App not installed

We could not synchronize checks via GitHub's checks API since Scrutinizer's GitHub App is not installed for this repository.

Install GitHub App

Completed
Push — master ( f35a35...781975 )
by Cristian
04:48
created

Fields::addField()   C

Complexity

Conditions 8
Paths 72

Size

Total Lines 45
Code Lines 24

Duplication

Lines 0
Ratio 0 %

Importance

Changes 0
Metric Value
cc 8
eloc 24
nc 72
nop 2
dl 0
loc 45
rs 5.3846
c 0
b 0
f 0
1
<?php
2
3
namespace Backpack\CRUD\PanelTraits;
4
5
trait Fields
6
{
7
    // ------------
8
    // FIELDS
9
    // ------------
10
11
    /**
12
     * Add a field to the create/update form or both.
13
     *
14
     * @param string   $form    The form to add the field to (create/update/both)
15
     */
16
    public function addField($field, $form = 'both')
17
    {
18
        // if the field_defition_array array is a string, it means the programmer was lazy and has only passed the name
19
        // set some default values, so the field will still work
20
        if (is_string($field)) {
21
            $complete_field_array['name'] = $field;
0 ignored issues
show
Coding Style Comprehensibility introduced by
$complete_field_array was never initialized. Although not strictly required by PHP, it is generally a good practice to add $complete_field_array = 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...
22
        } else {
23
            $complete_field_array = $field;
24
        }
25
26
        // if the label is missing, we should set it
27
        if (! isset($complete_field_array['label'])) {
28
            $complete_field_array['label'] = ucfirst($complete_field_array['name']);
29
        }
30
31
        // if the field type is missing, we should set it
32
        if (! isset($complete_field_array['type'])) {
33
            $complete_field_array['type'] = $this->getFieldTypeFromDbColumnType($complete_field_array['name']);
0 ignored issues
show
Bug introduced by
It seems like getFieldTypeFromDbColumnType() 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
36
        // if a tab was mentioned, we should enable it
37
        if (isset($complete_field_array['tab'])) {
38
            if (! $this->tabsEnabled()) {
0 ignored issues
show
Bug introduced by
It seems like tabsEnabled() 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
                $this->enableTabs();
0 ignored issues
show
Bug introduced by
It seems like enableTabs() 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...
40
            }
41
        }
42
43
        // store the field information into the correct variable on the CRUD object
44
        switch (strtolower($form)) {
45
            case 'create':
46
                $this->create_fields[$complete_field_array['name']] = $complete_field_array;
0 ignored issues
show
Bug introduced by
The property create_fields 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...
47
                break;
48
49
            case 'update':
50
                $this->update_fields[$complete_field_array['name']] = $complete_field_array;
0 ignored issues
show
Bug introduced by
The property update_fields 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...
51
                break;
52
53
            default:
54
                $this->create_fields[$complete_field_array['name']] = $complete_field_array;
55
                $this->update_fields[$complete_field_array['name']] = $complete_field_array;
56
                break;
57
        }
58
59
        return $this;
60
    }
61
62
    public function addFields($fields, $form = 'both')
63
    {
64
        if (count($fields)) {
65
            foreach ($fields as $field) {
66
                $this->addField($field, $form);
67
            }
68
        }
69
    }
70
71
    /**
72
     * Moves the recently added field to 'after' the $target_field.
73
     *
74
     * @param $target_field
75
     */
76
    public function afterField($target_field)
0 ignored issues
show
Coding Style Naming introduced by
The parameter $target_field is not named in camelCase.

This check marks parameter names that have not been written in camelCase.

In camelCase names are written without any punctuation, the start of each new word being marked by a capital letter. Thus the name database connection string becomes databaseConnectionString.

Loading history...
77
    {
78 View Code Duplication
        foreach ($this->create_fields as $field => $value) {
0 ignored issues
show
Duplication introduced by
This code seems to be duplicated across your project.

Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation.

You can also find more detailed suggestions in the “Code” section of your repository.

Loading history...
79
            if ($value['name'] == $target_field) {
80
                array_splice($this->create_fields, $field + 1, 0, [$field => array_pop($this->create_fields)]);
81
                break;
82
            }
83
        }
84 View Code Duplication
        foreach ($this->update_fields as $field => $value) {
0 ignored issues
show
Duplication introduced by
This code seems to be duplicated across your project.

Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation.

You can also find more detailed suggestions in the “Code” section of your repository.

Loading history...
85
            if ($value['name'] == $target_field) {
86
                array_splice($this->update_fields, $field + 1, 0, [$field => array_pop($this->update_fields)]);
87
                break;
88
            }
89
        }
90
    }
91
92
    /**
93
     * Moves the recently added field to 'before' the $target_field.
94
     *
95
     * @param $target_field
96
     */
97
    public function beforeField($target_field)
0 ignored issues
show
Coding Style Naming introduced by
The parameter $target_field is not named in camelCase.

This check marks parameter names that have not been written in camelCase.

In camelCase names are written without any punctuation, the start of each new word being marked by a capital letter. Thus the name database connection string becomes databaseConnectionString.

Loading history...
98
    {
99
        $key = 0;
100 View Code Duplication
        foreach ($this->create_fields as $field => $value) {
0 ignored issues
show
Duplication introduced by
This code seems to be duplicated across your project.

Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation.

You can also find more detailed suggestions in the “Code” section of your repository.

Loading history...
101
            if ($value['name'] == $target_field) {
102
                array_splice($this->create_fields, $key, 0, [$field => array_pop($this->create_fields)]);
103
                break;
104
            }
105
            $key++;
106
        }
107
        $key = 0;
108 View Code Duplication
        foreach ($this->update_fields as $field => $value) {
0 ignored issues
show
Duplication introduced by
This code seems to be duplicated across your project.

Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation.

You can also find more detailed suggestions in the “Code” section of your repository.

Loading history...
109
            if ($value['name'] == $target_field) {
110
                array_splice($this->update_fields, $key, 0, [$field => array_pop($this->update_fields)]);
111
                break;
112
            }
113
            $key++;
114
        }
115
    }
116
117
    /**
118
     * Remove a certain field from the create/update/both forms by its name.
119
     *
120
     * @param string $name Field name (as defined with the addField() procedure)
121
     * @param string $form update/create/both
122
     */
123
    public function removeField($name, $form = 'both')
124
    {
125
        switch (strtolower($form)) {
126
            case 'create':
127
                array_forget($this->create_fields, $name);
128
                break;
129
130
            case 'update':
131
                array_forget($this->update_fields, $name);
132
                break;
133
134
            default:
135
                array_forget($this->create_fields, $name);
136
                array_forget($this->update_fields, $name);
137
                break;
138
        }
139
    }
140
141
    /**
142
     * Remove many fields from the create/update/both forms by their name.
143
     *
144
     * @param array  $array_of_names A simple array of the names of the fields to be removed.
145
     * @param string $form           update/create/both
146
     */
147
    public function removeFields($array_of_names, $form = 'both')
0 ignored issues
show
Coding Style Naming introduced by
The parameter $array_of_names is not named in camelCase.

This check marks parameter names that have not been written in camelCase.

In camelCase names are written without any punctuation, the start of each new word being marked by a capital letter. Thus the name database connection string becomes databaseConnectionString.

Loading history...
148
    {
149
        if (! empty($array_of_names)) {
150
            foreach ($array_of_names as $name) {
151
                $this->removeField($name, $form);
152
            }
153
        }
154
    }
155
156
    /**
157
     * Check if field is the first of its type in the given fields array.
158
     * It's used in each field_type.blade.php to determine wether to push the css and js content or not (we only need to push the js and css for a field the first time it's loaded in the form, not any subsequent times).
0 ignored issues
show
Coding Style introduced by
This line exceeds maximum limit of 120 characters; contains 219 characters

Overly long lines are hard to read on any screen. Most code styles therefor impose a maximum limit on the number of characters in a line.

Loading history...
159
     *
160
     * @param array $field        The current field being tested if it's the first of its type.
161
     * @param array $fields_array All the fields in that particular form.
162
     *
163
     * @return bool true/false
164
     */
165
    public function checkIfFieldIsFirstOfItsType($field, $fields_array)
0 ignored issues
show
Coding Style Naming introduced by
The parameter $fields_array is not named in camelCase.

This check marks parameter names that have not been written in camelCase.

In camelCase names are written without any punctuation, the start of each new word being marked by a capital letter. Thus the name database connection string becomes databaseConnectionString.

Loading history...
166
    {
167
        if ($field['name'] == $this->getFirstOfItsTypeInArray($field['type'], $fields_array)['name']) {
0 ignored issues
show
Bug introduced by
It seems like getFirstOfItsTypeInArray() 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...
Unused Code introduced by
This if statement, and the following return statement can be replaced with return $field['name'] ==...$fields_array)['name'];.
Loading history...
168
            return true;
169
        }
170
171
        return false;
172
    }
173
174
    /**
175
     * Order the fields in a certain way.
176
     *
177
     * @param [string] Column name.
178
     * @param [attributes and values array]
179
     */
180
    public function setFieldOrder($fields)
0 ignored issues
show
Unused Code introduced by
The parameter $fields is not used and could be removed.

This check looks from parameters that have been defined for a function or method, but which are not used in the method body.

Loading history...
181
    {
182
        // TODO
183
    }
184
185
    // ALIAS of setFieldOrder($fields)
186
    public function setFieldsOrder($fields)
187
    {
188
        $this->setFieldOrder($fields);
189
    }
190
191
    /**
192
     * Decode attributes that are casted as array/object/json in the model.
193
     * So that they are not json_encoded twice before they are stored in the db
194
     * (once by Backpack in front-end, once by Laravel Attribute Casting).
195
     */
196
    public function decodeJsonCastedAttributes($data, $form, $id = false)
0 ignored issues
show
Documentation introduced by
The return type could not be reliably inferred; please add a @return annotation.

Our type inference engine in quite powerful, but sometimes the code does not provide enough clues to go by. In these cases we request you to add a @return annotation as described here.

Loading history...
197
    {
198
        // get the right fields according to the form type (create/update)
199
        $fields = $this->getFields($form, $id);
0 ignored issues
show
Bug introduced by
It seems like getFields() 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...
200
        $casted_attributes = $this->model->getCastedAttributes();
0 ignored issues
show
Bug introduced by
The property model 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...
201
202
        foreach ($fields as $field) {
203
204
            // Test the field is castable
205
            if (isset($field['name']) && array_key_exists($field['name'], $casted_attributes)) {
206
207
                // Handle JSON field types
208
                $jsonCastables = ['array', 'object', 'json'];
209
                $fieldCasting = $casted_attributes[$field['name']];
210
211
                if (in_array($fieldCasting, $jsonCastables) && isset($data[$field['name']]) && ! empty($data[$field['name']]) && ! is_array($data[$field['name']])) {
0 ignored issues
show
Coding Style introduced by
This line exceeds maximum limit of 120 characters; contains 165 characters

Overly long lines are hard to read on any screen. Most code styles therefor impose a maximum limit on the number of characters in a line.

Loading history...
212
                    try {
213
                        $data[$field['name']] = json_decode($data[$field['name']]);
214
                    } catch (Exception $e) {
0 ignored issues
show
Bug introduced by
The class Backpack\CRUD\PanelTraits\Exception does not exist. Did you forget a USE statement, or did you not list all dependencies?

Scrutinizer analyzes your composer.json/composer.lock file if available to determine the classes, and functions that are defined by your dependencies.

It seems like the listed class was neither found in your dependencies, nor was it found in the analyzed files in your repository. If you are using some other form of dependency management, you might want to disable this analysis.

Loading history...
215
                        $data[$field['name']] = [];
216
                    }
217
                }
218
            }
219
        }
220
221
        return $data;
222
    }
223
224
    public function getCurrentFields()
0 ignored issues
show
Documentation introduced by
The return type could not be reliably inferred; please add a @return annotation.

Our type inference engine in quite powerful, but sometimes the code does not provide enough clues to go by. In these cases we request you to add a @return annotation as described here.

Loading history...
225
    {
226
        if ($this->entry) {
227
            return $this->getUpdateFields($this->entry->getKey());
0 ignored issues
show
Bug introduced by
The property entry 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...
Bug introduced by
It seems like getUpdateFields() 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...
228
        }
229
230
        return $this->getCreateFields();
0 ignored issues
show
Bug introduced by
It seems like getCreateFields() 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...
231
    }
232
233
    // ------------
234
    // TONE FUNCTIONS - UNDOCUMENTED, UNTESTED, SOME MAY BE USED
235
    // ------------
236
    // TODO: check them
237
238
    public function orderFields($order)
239
    {
240
        $this->setSort('fields', (array) $order);
0 ignored issues
show
Bug introduced by
It seems like setSort() 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...
241
    }
242
}
243