PaginateViewHelper::render() - Code Metrics - kitodo/kitodo-publication - Measure and Improve Code Quality continuously with Scrutinizer

PaginateViewHelper::render() A
last analyzed 2021-07-13 12:25 UTC

↳ Parent: PaginateViewHelper

Complexity

Conditions	1
Paths	1

Size

Total Lines	3
Code Lines	1

Duplication

Lines	0
Ratio	0 %

Importance

Changes	1
Bugs	0	Features	0

Metric	Value
eloc	1
dl	0
loc	3
rs	10
c	1
b	0
f	0
cc	1
nc	1
nop	0

<?php
namespace EWW\Dpf\ViewHelpers\Widget;

/*                                                                        *
 * This script is backported from the TYPO3 Flow package "TYPO3.Fluid".   *
 *                                                                        *
 * It is free software; you can redistribute it and/or modify it under    *
 * the terms of the GNU Lesser General Public License, either version 3   *
 *  of the License, or (at your option) any later version.                *
 *                                                                        *
 *                                                                        *
 * This script is distributed in the hope that it will be useful, but     *
 * WITHOUT ANY WARRANTY; without even the implied warranty of MERCHAN-    *
 * TABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser       *
 * General Public License for more details.                               *
 *                                                                        *
 * You should have received a copy of the GNU Lesser General Public       *
 * License along with the script.                                         *
 * If not, see http://www.gnu.org/licenses/lgpl.html                      *
 *                                                                        *
 * The TYPO3 project - inspiring people to share!                         *
 *                                                                        */

/*
 * This ViewHelper renders a Pagination of objects.
 *
 * = Examples =
 *
 * <code title="required arguments">
 * <f:widget.paginate objects="{blogs}" as="paginatedBlogs">
 * use {paginatedBlogs} as you used {blogs} before, most certainly inside
 * a <f:for> loop.
 * </f:widget.paginate>
 * </code>
 *
 * <code title="full configuration">
 * <f:widget.paginate objects="{blogs}" as="paginatedBlogs" configuration="{itemsPerPage: 5, insertAbove: 1, insertBelow: 0, maximumNumberOfLinks: 10}">
 * use {paginatedBlogs} as you used {blogs} before, most certainly inside
 * a <f:for> loop.
 * </f:widget.paginate>
 * </code>
 *
 * = Performance characteristics =
 *
 * In the above examples, it looks like {blogs} contains all Blog objects, thus
 * you might wonder if all objects were fetched from the database.
 * However, the blogs are NOT fetched from the database until you actually use them,
 * so the paginate ViewHelper will adjust the query sent to the database and receive
 * only the small subset of objects.
 * So, there is no negative performance overhead in using the Paginate Widget.
 *
 */
class PaginateViewHelper extends \TYPO3\CMS\Fluid\Core\Widget\AbstractWidgetViewHelper
{
    public function initializeArguments()
    {
        parent::initializeArguments();
        $this->registerArgument('objects', 'mixed', 'Object', true);
        $this->registerArgument('as', 'string', 'as', true);
        $this->registerArgument('configuration', 'array',
            'configuration',
            false,
            ['itemsPerPage' => 10, 'insertAbove' => false, 'insertBelow' => true, 'maximumNumberOfLinks' => 99]
        );
        $this->registerArgument('total', 'int', 'Object', true);
        $this->registerArgument('currentPage', 'int', 'as', true);
    }

    /**
     * @var \EWW\Dpf\ViewHelpers\Widget\Controller\PaginateController
     * @TYPO3\CMS\Extbase\Annotation\Inject
     */
    protected $controller;

    /**
     * @return string
     */
    public function render()
    {
        return $this->initiateSubRequest();

    }
}



1			<?php
2			namespace EWW\Dpf\ViewHelpers\Widget;
3
4			/* *
5			* This script is backported from the TYPO3 Flow package "TYPO3.Fluid". *
6			* *
7			* It is free software; you can redistribute it and/or modify it under *
8			* the terms of the GNU Lesser General Public License, either version 3 *
9			* of the License, or (at your option) any later version. *
10			* *
11			* *
12			* This script is distributed in the hope that it will be useful, but *
13			* WITHOUT ANY WARRANTY; without even the implied warranty of MERCHAN- *
14			* TABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser *
15			* General Public License for more details. *
16			* *
17			* You should have received a copy of the GNU Lesser General Public *
18			* License along with the script. *
19			* If not, see http://www.gnu.org/licenses/lgpl.html *
20			* *
21			* The TYPO3 project - inspiring people to share! *
22			* */
23
24			/*
25			* This ViewHelper renders a Pagination of objects.
26			*
27			* = Examples =
28			*
29			* <code title="required arguments">
30			* <f:widget.paginate objects="{blogs}" as="paginatedBlogs">
31			* use {paginatedBlogs} as you used {blogs} before, most certainly inside
32			* a <f:for> loop.
33			* </f:widget.paginate>
34			* </code>
35			*
36			* <code title="full configuration">
37			* <f:widget.paginate objects="{blogs}" as="paginatedBlogs" configuration="{itemsPerPage: 5, insertAbove: 1, insertBelow: 0, maximumNumberOfLinks: 10}">
38			* use {paginatedBlogs} as you used {blogs} before, most certainly inside
39			* a <f:for> loop.
40			* </f:widget.paginate>
41			* </code>
42			*
43			* = Performance characteristics =
44			*
45			* In the above examples, it looks like {blogs} contains all Blog objects, thus
46			* you might wonder if all objects were fetched from the database.
47			* However, the blogs are NOT fetched from the database until you actually use them,
48			* so the paginate ViewHelper will adjust the query sent to the database and receive
49			* only the small subset of objects.
50			* So, there is no negative performance overhead in using the Paginate Widget.
51			*
52			*/
53			class PaginateViewHelper extends \TYPO3\CMS\Fluid\Core\Widget\AbstractWidgetViewHelper
54			{
55			public function initializeArguments()
56			{
57			parent::initializeArguments();
58			$this->registerArgument('objects', 'mixed', 'Object', true);
59			$this->registerArgument('as', 'string', 'as', true);
60			$this->registerArgument('configuration', 'array',
61			'configuration',
62			false,
63			['itemsPerPage' => 10, 'insertAbove' => false, 'insertBelow' => true, 'maximumNumberOfLinks' => 99]
64			);
65			$this->registerArgument('total', 'int', 'Object', true);
66			$this->registerArgument('currentPage', 'int', 'as', true);
67			}
68
69			/**
70			* @var \EWW\Dpf\ViewHelpers\Widget\Controller\PaginateController
71			* @TYPO3\CMS\Extbase\Annotation\Inject
72			*/
73			protected $controller;
74
75			/**
76			* @return string
77			*/
78			public function render()
79			{
80			return $this->initiateSubRequest();
			0 ignored issues – show Bug Best Practice introduced 2019-05-02 14:00 UTC by Report Bug Copy Issue Report The expression `return $this->initiateSubRequest()` returns the type `TYPO3\CMS\Extbase\Mvc\ResponseInterface` which is incompatible with the documented return type `string`. Loading history...
81			}
82			}
83
84

kitodo / kitodo-publication

PaginateViewHelper::render() A last analyzed 2021-07-13 12:25 UTC

Complexity

Size

Duplication

Importance

Duplication Side-by-Side

Filter issues like

PaginateViewHelper::render() A
last analyzed 2021-07-13 12:25 UTC