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
Pull Request — master (#966)
by Cristian
03:02 queued 25s
created

Fields::moveField()   A

Complexity

Conditions 4
Paths 5

Size

Total Lines 18
Code Lines 10

Duplication

Lines 0
Ratio 0 %

Importance

Changes 0
Metric Value
cc 4
eloc 10
c 0
b 0
f 0
nc 5
nop 3
dl 0
loc 18
rs 9.2
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_definition_array array is a string, it means the programmer was lazy and has only passed the name
0 ignored issues
show
Coding Style introduced by
This line exceeds maximum limit of 120 characters; contains 121 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...
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 this is a relation type field and no corresponding model was specified, get it from the relation method
27
        // defined in the main model
28
        if (isset($complete_field_array['entity']) && ! isset($complete_field_array['model'])) {
29
            $complete_field_array['model'] = $this->getRelationModel($complete_field_array['entity']);
0 ignored issues
show
Bug introduced by
It seems like getRelationModel() 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...
30
        }
31
32
        // if the label is missing, we should set it
33
        if (! isset($complete_field_array['label'])) {
34
            $complete_field_array['label'] = ucfirst($complete_field_array['name']);
35
        }
36
37
        // if the field type is missing, we should set it
38
        if (! isset($complete_field_array['type'])) {
39
            $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...
40
        }
41
42
        // if a tab was mentioned, we should enable it
43
        if (isset($complete_field_array['tab'])) {
44
            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...
45
                $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...
46
            }
47
        }
48
49
        // store the field information into the correct variable on the CRUD object
50
        switch (strtolower($form)) {
51
            case 'create':
52
                $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...
53
                break;
54
55
            case 'update':
56
                $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...
57
                break;
58
59
            default:
60
                $this->create_fields[$complete_field_array['name']] = $complete_field_array;
61
                $this->update_fields[$complete_field_array['name']] = $complete_field_array;
62
                break;
63
        }
64
65
        return $this;
66
    }
67
68
    public function addFields($fields, $form = 'both')
69
    {
70
        if (count($fields)) {
71
            foreach ($fields as $field) {
72
                $this->addField($field, $form);
73
            }
74
        }
75
    }
76
77
    /**
78
     * Move the most recently added field after the given target field.
79
     *
80
     * @param string $targetFieldName The target field name.
81
     * @param string $form The CRUD form. Can be 'create', 'update' or 'both'. Default is 'both'.
82
     */
83
    public function afterField($targetFieldName, $form = 'both')
84
    {
85
        $this->moveFieldInForm($targetFieldName, $form, false);
86
    }
87
88
    /**
89
     * Move the most recently added field before the given target field.
90
     *
91
     * @param string $targetFieldName The target field name.
92
     * @param string $form The CRUD form. Can be 'create', 'update' or 'both'. Default is 'both'.
93
     */
94
    public function beforeField($targetFieldName, $form = 'both')
95
    {
96
        $this->moveFieldInForm($targetFieldName, $form);
97
    }
98
99
    /**
100
     * Move the most recently added field from a given form before or after the given target field. Default is before.
101
     *
102
     * @param string $targetFieldName The target field name.
103
     * @param string $form The CRUD form. Can be 'create', 'update' or 'both'. Default is 'both'.
104
     * @param bool $before If true, the field will be moved before the target field, otherwise it will be moved after it.
0 ignored issues
show
Coding Style introduced by
This line exceeds maximum limit of 120 characters; contains 121 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...
105
     */
106
    protected function moveFieldInForm($targetFieldName, $form = 'both', $before = true)
107
    {
108
        switch ($form) {
109
            case 'create':
110
                $this->moveField($this->create_fields, $targetFieldName, $before);
111
                break;
112
            case 'update':
113
                $this->moveField($this->update_fields, $targetFieldName, $before);
114
                break;
115
            default:
116
                $this->moveField($this->create_fields, $targetFieldName, $before);
117
                $this->moveField($this->update_fields, $targetFieldName, $before);
118
                break;
119
        }
120
    }
121
122
    /**
123
     * Move the most recently added field before or after the given target field. Default is before.
124
     *
125
     * @param array $fields The form fields.
126
     * @param string $targetFieldName The target field name.
127
     * @param bool $before If true, the field will be moved before the target field, otherwise it will be moved after it.
0 ignored issues
show
Coding Style introduced by
This line exceeds maximum limit of 120 characters; contains 121 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...
128
     */
129
    private function moveField(&$fields, $targetFieldName, $before = true)
130
    {
131
        if (array_key_exists($targetFieldName, $fields)) {
132
            $targetFieldPosition = $before ? array_search($targetFieldName, array_keys($fields))
133
                : array_search($targetFieldName, array_keys($fields)) + 1;
134
135
            if ($targetFieldPosition >= (count($fields) - 1)) {
136
                // target field name is same as element
137
                return;
138
            }
139
140
            $element = array_pop($fields);
141
            $beginningArrayPart = array_slice($fields, 0, $targetFieldPosition, true);
142
            $endingArrayPart = array_slice($fields, $targetFieldPosition, null, true);
143
144
            $fields = array_merge($beginningArrayPart, [$element['name'] => $element], $endingArrayPart);
145
        }
146
    }
147
148
    /**
149
     * Remove a certain field from the create/update/both forms by its name.
150
     *
151
     * @param string $name Field name (as defined with the addField() procedure)
152
     * @param string $form update/create/both
153
     */
154
    public function removeField($name, $form = 'both')
155
    {
156
        switch (strtolower($form)) {
157
            case 'create':
158
                array_forget($this->create_fields, $name);
159
                break;
160
161
            case 'update':
162
                array_forget($this->update_fields, $name);
163
                break;
164
165
            default:
166
                array_forget($this->create_fields, $name);
167
                array_forget($this->update_fields, $name);
168
                break;
169
        }
170
    }
171
172
    /**
173
     * Remove many fields from the create/update/both forms by their name.
174
     *
175
     * @param array  $array_of_names A simple array of the names of the fields to be removed.
176
     * @param string $form           update/create/both
177
     */
178
    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...
179
    {
180
        if (! empty($array_of_names)) {
181
            foreach ($array_of_names as $name) {
182
                $this->removeField($name, $form);
183
            }
184
        }
185
    }
186
187
    /**
188
     * Check if field is the first of its type in the given fields array.
189
     * 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...
190
     *
191
     * @param array $field        The current field being tested if it's the first of its type.
192
     * @param array $fields_array All the fields in that particular form.
193
     *
194
     * @return bool true/false
195
     */
196
    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...
197
    {
198
        $first_field = $this->getFirstOfItsTypeInArray($field['type'], $fields_array);
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...
199
200
        if ($field['name'] == $first_field['name']) {
0 ignored issues
show
Unused Code introduced by
This if statement, and the following return statement can be replaced with return $field['name'] == $first_field['name'];.
Loading history...
201
            return true;
202
        }
203
204
        return false;
205
    }
206
207
    /**
208
     * Order the fields in a certain way.
209
     *
210
     * @param [string] Column name.
211
     * @param [attributes and values array]
212
     */
213
    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...
214
    {
215
        // TODO
216
    }
217
218
    // ALIAS of setFieldOrder($fields)
219
    public function setFieldsOrder($fields)
220
    {
221
        $this->setFieldOrder($fields);
222
    }
223
224
    /**
225
     * Decode attributes that are casted as array/object/json in the model.
226
     * So that they are not json_encoded twice before they are stored in the db
227
     * (once by Backpack in front-end, once by Laravel Attribute Casting).
228
     */
229
    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...
230
    {
231
        // get the right fields according to the form type (create/update)
232
        $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...
233
        $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...
234
235
        foreach ($fields as $field) {
236
237
            // Test the field is castable
238
            if (isset($field['name']) && array_key_exists($field['name'], $casted_attributes)) {
239
240
                // Handle JSON field types
241
                $jsonCastables = ['array', 'object', 'json'];
242
                $fieldCasting = $casted_attributes[$field['name']];
243
244
                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...
245
                    try {
246
                        $data[$field['name']] = json_decode($data[$field['name']]);
247
                    } 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...
248
                        $data[$field['name']] = [];
249
                    }
250
                }
251
            }
252
        }
253
254
        return $data;
255
    }
256
257
    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...
258
    {
259
        if ($this->entry) {
260
            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...
261
        }
262
263
        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...
264
    }
265
266
    // ------------
267
    // TONE FUNCTIONS - UNDOCUMENTED, UNTESTED, SOME MAY BE USED
268
    // ------------
269
    // TODO: check them
270
271
    public function orderFields($order)
272
    {
273
        $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...
274
    }
275
}
276