GitHub Access Token became invalid

It seems like the GitHub access token used for retrieving details about this repository from GitHub became invalid. This might prevent certain types of inspections from being run (in particular, everything related to pull requests).
Please ask an admin of your repository to re-new the access token on this website.
Passed
Push — master ( 083d1a...28e483 )
by cao
03:15
created

WhereRule::whereArgs()   A

Complexity

Conditions 1
Paths 1

Size

Total Lines 4
Code Lines 3

Duplication

Lines 4
Ratio 100 %

Code Coverage

Tests 0
CRAP Score 2

Importance

Changes 0
Metric Value
cc 1
eloc 3
nc 1
nop 1
dl 4
loc 4
ccs 0
cts 3
cp 0
crap 2
rs 10
c 0
b 0
f 0
1
<?php
0 ignored issues
show
Coding Style Compatibility introduced by
For compatibility and reusability of your code, PSR1 recommends that a file should introduce either new symbols (like classes, functions, etc.) or have side-effects (like outputting something, or including other files), but not both at the same time. The first symbol is defined on line 12 and the first side effect is on line 10.

The PSR-1: Basic Coding Standard recommends that a file should either introduce new symbols, that is classes, functions, constants or similar, or have side effects. Side effects are anything that executes logic, like for example printing output, changing ini settings or writing to a file.

The idea behind this recommendation is that merely auto-loading a class should not change the state of an application. It also promotes a cleaner style of programming and makes your code less prone to errors, because the logic is not spread out all over the place.

To learn more about the PSR-1, please see the PHP-FIG site on the PSR-1.

Loading history...
2
namespace PhpBoot\DB\rules\basic;
3
4
use PhpBoot\DB\Context;
5
use PhpBoot\DB\impls\ExecImpl;
6
use PhpBoot\DB\impls\LimitImpl;
7
use PhpBoot\DB\impls\OrderByImpl;
8
use PhpBoot\DB\impls\ExecResult;
9
use PhpBoot\DB\impls\WhereImpl;
10 1
require_once dirname(__DIR__).'/impls.php';
11
12
class BasicRule
13
{
14 42
    public function __construct(Context $context){
15 42
        $this->context = $context;
16 42
    }
17
18
19
    /**
20
     * @var Context
21
     */
22
    public $context;
23
}
24
25
class ExecRule extends BasicRule
0 ignored issues
show
Coding Style Compatibility introduced by
PSR1 recommends that each class should be in its own file to aid autoloaders.

Having each class in a dedicated file usually plays nice with PSR autoloaders and is therefore a well established practice. If you use other autoloaders, you might not want to follow this rule.

Loading history...
26
{
27
    /**
28
     * Execute sql
29
     * @return ExecResult
30
     */
31 22
    public function exec() {
32 22
        return ExecImpl::exec($this->context);
33
    }
34
}
35
36
class LimitRule extends ExecRule
0 ignored issues
show
Coding Style Compatibility introduced by
PSR1 recommends that each class should be in its own file to aid autoloaders.

Having each class in a dedicated file usually plays nice with PSR autoloaders and is therefore a well established practice. If you use other autoloaders, you might not want to follow this rule.

Loading history...
37
{
38
    /**
39
     * limit(1) => "LIMIT 1"
40
     * @param int $size
41
     * @return \PhpBoot\DB\rules\basic\ExecRule
42
     */
43 3
    public function limit($size) {
44 3
        LimitImpl::limit($this->context, $size);
45 3
        return new ExecRule($this->context);
46
    }
47
}
48
49
class OrderByRule extends LimitRule
0 ignored issues
show
Coding Style Compatibility introduced by
PSR1 recommends that each class should be in its own file to aid autoloaders.

Having each class in a dedicated file usually plays nice with PSR autoloaders and is therefore a well established practice. If you use other autoloaders, you might not want to follow this rule.

Loading history...
50
{
51 15
    public function __construct($context){
52 15
        parent::__construct($context);
53 15
        $this->impl = new OrderByImpl();
54 15
    }
55
//    /**
0 ignored issues
show
Unused Code Comprehensibility introduced by
45% 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...
56
//     * orderByArgs(['column0', 'column1'=>Sql::ORDER_BY_ASC]) => "ORDER BY column0,column1 ASC"
57
//     * @param array $orders
58
//     * @return \PhpBoot\DB\rules\basic\LimitRule
59
//     */
60
//    public function orderByArgs($orders) {
61
//        $this->impl->orderByArgs($this->context, $orders);
62
//        return new LimitRule($this->context);
63
//    }
64
    /**
65
     * 
66
     * orderBy('column') => "ORDER BY column"
67
     * orderBy('column', Sql::ORDER_BY_ASC) => "ORDER BY column ASC"
68
     * orderBy('column0')->orderBy('column1') => "ORDER BY column0, column1"
69
     * orderBy(['column0', 'column1'=>Sql::ORDER_BY_ASC]) => "ORDER BY column0,column1 ASC"
70
     * @param string $column
71
     * @param string $order Sql::ORDER_BY_ASC or Sql::ORDER_BY_DESC
72
     * 
73
     * @return \PhpBoot\DB\rules\basic\LimitRule
74
     */
75 4
    public function orderBy($column, $order=null) {
76 4
        $this->impl->orderBy($this->context, $column, $order);
77 4
        return new LimitRule($this->context);
78
    }
79
    private $impl;
80
}
81
82
class WhereRule extends OrderByRule
0 ignored issues
show
Coding Style Compatibility introduced by
PSR1 recommends that each class should be in its own file to aid autoloaders.

Having each class in a dedicated file usually plays nice with PSR autoloaders and is therefore a well established practice. If you use other autoloaders, you might not want to follow this rule.

Loading history...
83
{
84
    /**
85
     * 
86
     * where('a=?', 1) => "WHERE a=1"
87
     * where('a=?', Sql::raw('now()')) => "WHERE a=now()"
88
     * where('a IN (?)',  [1, 2]) => "WHERE a IN (1,2)"
89
     *
90
     * where([
91
     *      'a'=>1,
92
     *      'b'=>['IN'=>[1,2]]
93
     *      'c'=>['BETWEEN'=>[1,2]]
94
     *      'd'=>['<>'=>1]
95
     *      ])
96
     *      =>
97
     *      "WHERE a=1 AND b IN(1,2) AND c BETWEEN 1 AND 2 AND d<>1"
98
     *
99
     * @param string|array $expr
100
     * @param mixed $_
101
     * @return \PhpBoot\DB\rules\basic\OrderByRule
102
     */
103 13
    public function where($expr, $_= null) {
0 ignored issues
show
Unused Code introduced by
The parameter $_ 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...
104 13
        WhereImpl::where($this->context, $expr, array_slice(func_get_args(), 1));
105 13
        return new OrderByRule($this->context);
106
    }
107
}