PaginateTrait::paginate() - Code Metrics - Inspection of "new dependencies version" - Cherry-Pie/Jarboe - Measure and Improve Code Quality continuously with Scrutinizer

Completed

Push — master ( ad2c0d...49711d )

by Yaro

created 2019-10-28 16:20 UTC

PaginateTrait::paginate() A

↳ Parent: PaginateTrait

Complexity

Conditions	4
Paths	4

Size

Total Lines

Duplication

Lines	0
Ratio	0 %

Code Coverage

Tests	0
CRAP Score	20

Importance

Changes

Metric	Value
dl	0
loc	16
ccs	0
cts	10
cp	0
rs	9.7333
c	0
b	0
f	0
cc	4
nc	4
nop	1
crap	20

<?php

namespace Yaro\Jarboe\Table\CrudTraits;

trait PaginateTrait
{
    private $rawPerPage;

    public function getRawPerPage()

    {
        return $this->rawPerPage;
    }

    /**
     * @param int|array $perPage
     */
    public function paginate($perPage)
    {
        $this->rawPerPage = $perPage;

        $storedPerPage = $this->getPerPageParam();
        if (is_array($perPage)) {
            $perPage = array_shift($perPage);
        }
        if (!$storedPerPage) {
            $this->setPerPageParam($perPage ?: $this->repo()->perPage());
            $storedPerPage = $perPage;
        }
        $this->repo()->perPage($storedPerPage);

        return $this;
    }

    abstract public function getPerPageParam();

    abstract public function setPerPageParam($perPage);

    abstract public function repo();

}


1			<?php
2
3			namespace Yaro\Jarboe\Table\CrudTraits;
4
5			trait PaginateTrait
6			{
7			private $rawPerPage;
8
9			public function getRawPerPage()
			0 ignored issues – show Documentation introduced 2019-10-28 16:30 UTC by Report Bug Copy Issue Report 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...
10			{
11			return $this->rawPerPage;
12			}
13
14			/**
15			* @param int\|array $perPage
16			*/
17			public function paginate($perPage)
18			{
19			$this->rawPerPage = $perPage;
20
21			$storedPerPage = $this->getPerPageParam();
22			if (is_array($perPage)) {
23			$perPage = array_shift($perPage);
24			}
25			if (!$storedPerPage) {
26			$this->setPerPageParam($perPage ?: $this->repo()->perPage());
27			$storedPerPage = $perPage;
28			}
29			$this->repo()->perPage($storedPerPage);
30
31			return $this;
32			}
33
34			abstract public function getPerPageParam();
			0 ignored issues – show Documentation introduced 2019-10-28 16:30 UTC by Report Bug Copy Issue Report For interfaces and abstract methods it is generally a good practice to add a `@return` annotation even if it is just `@return void` or `@return null`, so that implementors know what to do in the overridden method. For interface and abstract methods, it is impossible to infer the return type from the immediate code. In these cases, it is generally advisible to explicitly annotate these methods with a `@return` doc comment to communicate to implementors of these methods what they are expected to return. Loading history...
35			abstract public function setPerPageParam($perPage);
			0 ignored issues – show Documentation introduced 2019-10-28 16:30 UTC by Report Bug Copy Issue Report For interfaces and abstract methods it is generally a good practice to add a `@return` annotation even if it is just `@return void` or `@return null`, so that implementors know what to do in the overridden method. For interface and abstract methods, it is impossible to infer the return type from the immediate code. In these cases, it is generally advisible to explicitly annotate these methods with a `@return` doc comment to communicate to implementors of these methods what they are expected to return. Loading history...
36			abstract public function repo();
			0 ignored issues – show Documentation introduced 2019-10-28 16:30 UTC by Report Bug Copy Issue Report For interfaces and abstract methods it is generally a good practice to add a `@return` annotation even if it is just `@return void` or `@return null`, so that implementors know what to do in the overridden method. For interface and abstract methods, it is impossible to infer the return type from the immediate code. In these cases, it is generally advisible to explicitly annotate these methods with a `@return` doc comment to communicate to implementors of these methods what they are expected to return. Loading history...
37			}
38

Cherry-Pie / Jarboe

Push — master ( ad2c0d...49711d )

PaginateTrait::paginate() A

Complexity

Size

Duplication

Code Coverage

Importance

Duplication Side-by-Side

Filter issues like