Passed
Push — master ( b8296b...81a8b5 )
by Francis
01:16
created

RefactorCI::refactorObject()   C

Complexity

Conditions 15
Paths 49

Size

Total Lines 43
Code Lines 29

Duplication

Lines 0
Ratio 0 %

Importance

Changes 1
Bugs 0 Features 0
Metric Value
cc 15
eloc 29
c 1
b 0
f 0
nc 49
nop 2
dl 0
loc 43
rs 5.9166

How to fix   Complexity   

Long Method

Small methods make your code easier to understand, in particular if combined with a good name. Besides, if your method is small, finding a good name is usually much easier.

For example, if you find yourself adding comments to a method's body, this is usually a good sign to extract the commented part to a new method, and use the comment as a starting point when coming up with a good name for this new method.

Commonly applied refactorings include:

1
<?php
2
defined('BASEPATH') OR exit('No direct script access allowed');
3
4
class RefactorCI {
5
6
  /**
7
   * [private description]
8
   * @var [type]
0 ignored issues
show
Documentation Bug introduced by
The doc comment [type] at position 0 could not be parsed: Unknown type name '[' at position 0 in [type].
Loading history...
9
   */
10
  private $ci;
11
12
  private $primaryKey;
13
14
  function __construct($params=null) {
15
    $this->ci =& get_instance();
0 ignored issues
show
Bug introduced by
The function get_instance was not found. Maybe you did not declare it correctly or list all dependencies? ( Ignorable by Annotation )

If this is a false-positive, you can also ignore this issue in your code via the ignore-call  annotation

15
    $this->ci =& /** @scrutinizer ignore-call */ get_instance();
Loading history...
16
    $this->ci->load->config("refactor", false, true);
17
    $this->init($params == null ? [] : $params);
18
  }
19
20
  public function init(array $params):void {
21
    $this->primaryKey = $params['primary_key'] ?? 'id';
22
  }
23
  /**
24
   * [refactorObject description]
25
   * @param array  $object   [description]
26
   * @param string $ruleName [description]
27
   */
28
  function refactorObject(array &$object, string $ruleName):void {
0 ignored issues
show
Best Practice introduced by
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
29
    $rule = $this->ci->config->item("refactor_$ruleName");
30
    if ($rule == null) return; // No need to go further as rule doesn't exist.
31
    // Unset
32
    if (isset($rule['unset'])) {
33
      $this->unset_values($object, $rule);
34
    }
35
    // Replace
36
    if (isset($rule['replace'])) {
37
      $this->replace_fields($object, $rule);
38
    }
39
    // Bools
40
    if (isset($rule['bools'])) {
41
      foreach($rule['bools'] as $boolKey) {
42
        $object[$boolKey] = $object[$boolKey] == 1 || $object[$boolKey] == 'true';
43
      }
44
    }
45
    // Objects
46
    if (isset($rule['objects'])) {
47
      foreach($rule['objects'] as $field => $data) {
48
        $ids = json_decode($object[$field]);
49
        if (is_scalar($ids)) {
50
          // JSON Array wasn't supplied. Let's treat it as a scaler ID.
51
          $this->ci->db->where($this->primaryKey, $ids);
52
          $query = $this->ci->db->get($data['table']);
53
          if ($query->num_rows() == 0) {
54
            $object[$field] = json_encode (json_decode ("{}"));
55
            continue;
56
          }
57
          $object[$field] = $query->result_array()[0];
58
          if (isset($data['refactor'])) $this->run($object[$field], $data['refactor']);
0 ignored issues
show
Bug introduced by
The method run() does not exist on RefactorCI. ( Ignorable by Annotation )

If this is a false-positive, you can also ignore this issue in your code via the ignore-call  annotation

58
          if (isset($data['refactor'])) $this->/** @scrutinizer ignore-call */ run($object[$field], $data['refactor']);

This check looks for calls to methods that do not seem to exist on a given type. It looks for the method on the type itself as well as in inherited classes or implemented interfaces.

This is most likely a typographical error or the method has been renamed.

Loading history...
59
          continue;
60
        }
61
        $object[$field] = [];
62
        foreach($ids as $id) {
63
          $this->ci->db->where($this->primaryKey, $id);
64
          $query = $this->ci->db->get($data['table']);
65
          if ($query->num_rows() == 0) {
66
            continue;
67
          }
68
          $object[$field][] = $query->result_array()[0];
69
          // Recursion
70
          if (isset($data['refactor'])) $this->refactorObject($object[$field][count($object[$field]) - 1], $data['refactor']);
71
        }
72
      }
73
    }
74
  }
75
  /**
76
   * [unset_values u]
77
   * @param array  $object Object to Refactor.
78
   * @param array  $rule   Rule data, containing keys to unset in  the given
79
   *                       associative array.
80
   */
81
  private function unset_values(array &$object, &$rule):void {
82
    foreach($rule['unset'] as $key) {
83
      unset($object[$key]);
84
    }
85
  }
86
  /**
87
   * [replace_fields description]
88
   * @param array  $object [description]
89
   * @param [type] $rule   [description]
0 ignored issues
show
Documentation Bug introduced by
The doc comment [type] at position 0 could not be parsed: Unknown type name '[' at position 0 in [type].
Loading history...
90
   */
91
  private function replace_fields(array &$object, &$rule):void {
92
    foreach ($rule['replace'] as $oldKey => $newKey) {
93
      $object[$newKey] = $object[$oldKey];
94
      unset($object[$oldKey]);
95
    }
96
  }
97
}
98
?>
0 ignored issues
show
Best Practice introduced by
It is not recommended to use PHP's closing tag ?> in files other than templates.

Using a closing tag in PHP files that only contain PHP code is not recommended as you might accidentally add whitespace after the closing tag which would then be output by PHP. This can cause severe problems, for example headers cannot be sent anymore.

A simple precaution is to leave off the closing tag as it is not required, and it also has no negative effects whatsoever.

Loading history...
99