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 (#282)
by Owen
02:25
created

Fields::mutateFieldData()   B

Complexity

Conditions 8
Paths 5

Size

Total Lines 18
Code Lines 9

Duplication

Lines 0
Ratio 0 %

Importance

Changes 1
Bugs 1 Features 0
Metric Value
cc 8
eloc 9
nc 5
nop 2
dl 0
loc 18
rs 7.7777
c 1
b 1
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
        // store the field information into the correct variable on the CRUD object
37
        switch (strtolower($form)) {
38
            case 'create':
39
                $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...
40
                break;
41
42
            case 'update':
43
                $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...
44
                break;
45
46
            default:
47
                $this->create_fields[$complete_field_array['name']] = $complete_field_array;
48
                $this->update_fields[$complete_field_array['name']] = $complete_field_array;
49
                break;
50
        }
51
    }
52
53
    public function addFields($fields, $form = 'both')
54
    {
55
        if (count($fields)) {
56
            foreach ($fields as $field) {
57
                $this->addField($field, $form);
58
            }
59
        }
60
    }
61
62
    /**
63
     * Remove a certain field from the create/update/both forms by its name.
64
     *
65
     * @param string $name Field name (as defined with the addField() procedure)
66
     * @param string $form update/create/both
67
     */
68
    public function removeField($name, $form = 'both')
69
    {
70
        switch (strtolower($form)) {
71
            case 'create':
72
                array_forget($this->create_fields, $name);
73
                break;
74
75
            case 'update':
76
                array_forget($this->update_fields, $name);
77
                break;
78
79
            default:
80
                array_forget($this->create_fields, $name);
81
                array_forget($this->update_fields, $name);
82
                break;
83
        }
84
    }
85
86
    /**
87
     * Remove many fields from the create/update/both forms by their name.
88
     *
89
     * @param array  $array_of_names A simple array of the names of the fields to be removed.
90
     * @param string $form           update/create/both
91
     */
92
    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...
93
    {
94
        if (! empty($array_of_names)) {
95
            foreach ($array_of_names as $name) {
96
                $this->removeField($name, $form);
97
            }
98
        }
99
    }
100
101
    /**
102
     * Check if field is the first of its type in the given fields array.
103
     * 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...
104
     *
105
     * @param array $field        The current field being tested if it's the first of its type.
106
     * @param array $fields_array All the fields in that particular form.
107
     *
108
     * @return bool true/false
109
     */
110
    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...
111
    {
112
        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...
113
            return true;
114
        }
115
116
        return false;
117
    }
118
119
    /**
120
     * Order the fields in a certain way.
121
     *
122
     * @param [string] Column name.
123
     * @param [attributes and values array]
124
     */
125
    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...
126
    {
127
        // TODO
128
    }
129
130
    // ALIAS of setFieldOrder($fields)
131
    public function setFieldsOrder($fields)
132
    {
133
        $this->setFieldOrder($fields);
134
    }
135
136
    // ------------
137
    // TONE FUNCTIONS - UNDOCUMENTED, UNTESTED, SOME MAY BE USED
138
    // ------------
139
    // TODO: check them
140
141
    public function orderFields($order)
142
    {
143
        $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...
144
    }
145
146
    public function mutateFieldData($data, $fields)
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...
147
    {
148
        foreach ($this->{$fields} as $field) {
149
150
            // Handle table field type mutation
151
            if (isset($field['type']) && $field['type'] == 'table') {
152
                if (isset($data[$field['name']]) && is_string($field['name']) && ! empty($field['name'])) {
153
                    try {
154
                        $data[$field['name']] = json_decode($data[$field['name']]);
155
                    } 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...
156
                        $data[$field['name']] = [];
157
                    }
158
                }
159
            }
160
        }
161
162
        return $data;
163
    }
164
}
165