Completed
Push — master ( 036d78...0a4fc2 )
by Ievgen
05:10
created

UpdateOperation   A

Complexity

Total Complexity 9

Size/Duplication

Total Lines 76
Duplicated Lines 0 %

Coupling/Cohesion

Components 0
Dependencies 1

Importance

Changes 0
Metric Value
dl 0
loc 76
rs 10
c 0
b 0
f 0
wmc 9
lcom 0
cbo 1
1
<?php
2
3
use einfach\operation\Railway;
4
use function einfach\operation\response\ok;
5
use function einfach\operation\response\error;
6
7
class UpdateOperation implements \einfach\operation\IOperation
0 ignored issues
show
Coding Style Compatibility introduced by
PSR1 recommends that each class must be in a namespace of at least one level to avoid collisions.

You can fix this by adding a namespace to your class:

namespace YourVendor;

class YourClass { }

When choosing a vendor namespace, try to pick something that is not too generic to avoid conflicts with other libraries.

Loading history...
8
{
9
    /**
10
     * @param $params
11
     * @return \einfach\operation\Result
12
     */
13
    public public function __invoke($params)
0 ignored issues
show
Bug introduced by
This code did not parse for me. Apparently, there is an error somewhere around this line:

Multiple access type modifiers are not allowed
Loading history...
14
    {
15
        $result = (new Railway)
16
            ->step(function ($params) {
17
                echo "Hey {$params['name']}. Say hello to anonymous function!";
18
                //return error('Early fail');
0 ignored issues
show
Unused Code Comprehensibility introduced by
72% of this comment could be valid code. Did you maybe forget this after debugging?

Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it.

The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production.

This check looks for comments that seem to be mostly valid code and reports them.

Loading history...
19
                return ok(['newParam' => 'newValue']);
20
            })
21
            ->step([$this, 'nestedRailway'])
22
            ->step([$this, 'castRequest'])
23
            ->step([$this, 'validateRequest'])
24
            ->step([$this, 'findUser'])
25
            ->step([$this, 'updateDB'])
26
            ->tryCatch([$this, 'sendNotification'])
27
            ->always([$this, 'writeLog'])
28
            ->failure([$this, 'notifyAdmin'])
29
            ->runWithParams($params);
30
31
        return $result;
32
    }
33
34
    public function nestedRailway($params){
35
        return (new Railway)
36
            ->step(function ($params){
37
                return error('Nested Railway failed!');
38
                return ok(['nestedRwParam' => 'nestedRwValue']);
39
            })
40
            ->runWithParams($params);
41
    }
42
43
    public function castRequest($params)
44
    {
45
        return ok();
46
    }
47
48
    public function validateRequest($params)
49
    {
50
        return ok();
51
    }
52
53
    public function findUser($params)
54
    {
55
        // pretend I am doing a query
56
        // $user = DB::findById($params['id']);
0 ignored issues
show
Unused Code Comprehensibility introduced by
60% of this comment could be valid code. Did you maybe forget this after debugging?

Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it.

The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production.

This check looks for comments that seem to be mostly valid code and reports them.

Loading history...
57
        $user = (object) ['id' => 123, 'name' => 'Eugene', 'phone' => '111111'];
58
       return ok(['model' => $user]);
59
        //return error('User not found!');
0 ignored issues
show
Unused Code Comprehensibility introduced by
72% of this comment could be valid code. Did you maybe forget this after debugging?

Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it.

The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production.

This check looks for comments that seem to be mostly valid code and reports them.

Loading history...
60
    }
61
62
    public function updateDB($params)
63
    {
64
        return ok();
65
    }
66
67
    public function sendNotification($params)
68
    {
69
        //throw new \Exception("Hey there, Exception!");
0 ignored issues
show
Unused Code Comprehensibility introduced by
67% of this comment could be valid code. Did you maybe forget this after debugging?

Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it.

The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production.

This check looks for comments that seem to be mostly valid code and reports them.

Loading history...
70
        return ok();
71
    }
72
73
    public function writeLog($params)
74
    {
75
76
    }
77
78
    public function notifyAdmin($params)
79
    {
80
81
    }
82
}
83
84
85
/*
0 ignored issues
show
Unused Code Comprehensibility introduced by
53% of this comment could be valid code. Did you maybe forget this after debugging?

Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it.

The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production.

This check looks for comments that seem to be mostly valid code and reports them.

Loading history...
86
87
$castRequest = castRequest($request);   // always success (one-way track) // Success
88
$validRequest = validateRequest($castRequest);  // true or false (two ways tracks)  // Step
89
$dbResult = updateDB($validRequest);  // does not return (dead-end track) // Step
90
sendNotification($dbResult, $validRequest);  // try catch // TryCatch
91
writeLog($dbResult, $validRequest); // supervisory (do smth for both tracks) // Proxy
92
render($dbResult, $validRequest);
93
94
*/
95
96
97
//->wrap(function ($params) use ($dbConn) {
0 ignored issues
show
Unused Code Comprehensibility introduced by
61% of this comment could be valid code. Did you maybe forget this after debugging?

Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it.

The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production.

This check looks for comments that seem to be mostly valid code and reports them.

Loading history...
98
//    /** @var $pipe Pipe */
99
//    $params['dbConn'] = $dbConn;
100
//
101
//    return Pipe::with($params)
102
//        ->tryCatch(function ($params) {
103
//            return $params['dbConn']->beginTransaction();
104
//        })
105
//        ->step(function ($params) {
106
//            return $params['dbConn']->createCommand('SQL #1')->execute();
107
//        })
108
//        ->step(function ($params) {
109
//            return $params['dbConn']->createCommand('SQL #2')->execute();
110
//        })
111
//        ->tryCatch(function ($params) {
112
//            return $params['transaction']->commit();
113
//        })
114
//        ->fail(function ($params) {
115
//            return $params['transaction']->rollBack();
116
//        })
117
//        ->run();
118
//})
119