Completed
Push — master ( 089040...09b515 )
by Aimeos
03:33
created

Standard::getChildItems()   A

Complexity

Conditions 2
Paths 2

Size

Total Lines 23
Code Lines 13

Duplication

Lines 0
Ratio 0 %

Importance

Changes 2
Bugs 0 Features 0
Metric Value
cc 2
eloc 13
c 2
b 0
f 0
nc 2
nop 2
dl 0
loc 23
rs 9.8333
1
<?php
2
3
/**
4
 * @license LGPLv3, http://opensource.org/licenses/LGPL-3.0
5
 * @copyright Aimeos (aimeos.org), 2015-2020
6
 * @package Admin
7
 * @subpackage JsonAdm
8
 */
9
10
11
namespace Aimeos\Admin\JsonAdm\Order\Base;
12
13
use \Psr\Http\Message\ServerRequestInterface;
14
use \Psr\Http\Message\ResponseInterface;
15
16
17
/**
18
 * JSON API order client
19
 *
20
 * @package Admin
21
 * @subpackage JsonAdm
22
 */
23
class Standard
24
	extends \Aimeos\Admin\JsonAdm\Standard
25
	implements \Aimeos\Admin\JsonAdm\Common\Iface
26
{
27
	/** admin/jsonadm/order/base/decorators/excludes
28
	 * Excludes decorators added by the "common" option from the JSON API clients
29
	 *
30
	 * Decorators extend the functionality of a class by adding new aspects
31
	 * (e.g. log what is currently done), executing the methods of the underlying
32
	 * class only in certain conditions (e.g. only for logged in users) or
33
	 * modify what is returned to the caller.
34
	 *
35
	 * This option allows you to remove a decorator added via
36
	 * "admin/jsonadm/common/decorators/default" before they are wrapped
37
	 * around the Jsonadm client.
38
	 *
39
	 *  admin/jsonadm/decorators/excludes = array( 'decorator1' )
40
	 *
41
	 * This would remove the decorator named "decorator1" from the list of
42
	 * common decorators ("\Aimeos\Admin\JsonAdm\Common\Decorator\*") added via
43
	 * "admin/jsonadm/common/decorators/default" for the JSON API client.
44
	 *
45
	 * @param array List of decorator names
46
	 * @since 2016.01
47
	 * @category Developer
48
	 * @see admin/jsonadm/common/decorators/default
49
	 * @see admin/jsonadm/order/base/decorators/global
50
	 * @see admin/jsonadm/order/base/decorators/local
51
	 */
52
53
	/** admin/jsonadm/order/base/decorators/global
54
	 * Adds a list of globally available decorators only to the Jsonadm client
55
	 *
56
	 * Decorators extend the functionality of a class by adding new aspects
57
	 * (e.g. log what is currently done), executing the methods of the underlying
58
	 * class only in certain conditions (e.g. only for logged in users) or
59
	 * modify what is returned to the caller.
60
	 *
61
	 * This option allows you to wrap global decorators
62
	 * ("\Aimeos\Admin\Jsonadm\Common\Decorator\*") around the Jsonadm
63
	 * client.
64
	 *
65
	 *  admin/jsonadm/order/base/decorators/global = array( 'decorator1' )
66
	 *
67
	 * This would add the decorator named "decorator1" defined by
68
	 * "\Aimeos\Admin\Jsonadm\Common\Decorator\Decorator1" only to the
69
	 * "order/base" Jsonadm client.
70
	 *
71
	 * @param array List of decorator names
72
	 * @since 2016.01
73
	 * @category Developer
74
	 * @see admin/jsonadm/common/decorators/default
75
	 * @see admin/jsonadm/order/base/decorators/excludes
76
	 * @see admin/jsonadm/order/base/decorators/local
77
	 */
78
79
	/** admin/jsonadm/order/base/decorators/local
80
	 * Adds a list of local decorators only to the Jsonadm client
81
	 *
82
	 * Decorators extend the functionality of a class by adding new aspects
83
	 * (e.g. log what is currently done), executing the methods of the underlying
84
	 * class only in certain conditions (e.g. only for logged in users) or
85
	 * modify what is returned to the caller.
86
	 *
87
	 * This option allows you to wrap local decorators
88
	 * ("\Aimeos\Admin\Jsonadm\Order\Base\Decorator\*") around the Jsonadm
89
	 * client.
90
	 *
91
	 *  admin/jsonadm/order/base/decorators/local = array( 'decorator2' )
92
	 *
93
	 * This would add the decorator named "decorator2" defined by
94
	 * "\Aimeos\Admin\Jsonadm\Order\Base\Decorator\Decorator2" only to the
95
	 * "order/base" Jsonadm client.
96
	 *
97
	 * @param array List of decorator names
98
	 * @since 2016.01
99
	 * @category Developer
100
	 * @see admin/jsonadm/common/decorators/default
101
	 * @see admin/jsonadm/order/base/decorators/excludes
102
	 * @see admin/jsonadm/order/base/decorators/global
103
	 */
104
105
106
	/**
107
	 * Returns the requested resource or the resource list
108
	 *
109
	 * @param \Psr\Http\Message\ServerRequestInterface $request Request object
110
	 * @param \Psr\Http\Message\ResponseInterface $response Response object
111
	 * @return \Psr\Http\Message\ResponseInterface Modified response object
112
	 */
113
	public function get( ServerRequestInterface $request, ResponseInterface $response ) : \Psr\Http\Message\ResponseInterface
114
	{
115
		/** admin/jsonadm/partials/order/base/template-data
116
		 * Relative path to the data partial template file for the order base client
117
		 *
118
		 * Partials are templates which are reused in other templates and generate
119
		 * reoccuring blocks filled with data from the assigned values. The data
120
		 * partial creates the "data" part for the JSON API response.
121
		 *
122
		 * The partial template files are usually stored in the templates/partials/ folder
123
		 * of the core or the extensions. The configured path to the partial file must
124
		 * be relative to the templates/ folder, e.g. "partials/data-standard".
125
		 *
126
		 * @param string Relative path to the template file
127
		 * @since 2016.01
128
		 * @category Developer
129
		 */
130
		$this->getView()->assign( array( 'partial-data' => 'admin/jsonadm/partials/order/base/template-data' ) );
131
132
		return parent::get( $request, $response );
133
	}
134
135
136
	/**
137
	 * Retrieves the item or items and adds the data to the view
138
	 *
139
	 * @param \Aimeos\MW\View\Iface $view View instance
140
	 * @param \Psr\Http\Message\ServerRequestInterface $request Request object
141
	 * @param \Psr\Http\Message\ResponseInterface $response Response object
142
	 * @return \Psr\Http\Message\ResponseInterface Modified response object
143
	 */
144
	protected function getItems( \Aimeos\MW\View\Iface $view, ServerRequestInterface $request, ResponseInterface $response ) : \Psr\Http\Message\ResponseInterface
145
	{
146
		$context = $this->getContext();
147
		$manager = \Aimeos\MShop::create( $context, $this->getPath() );
148
		$search = $manager->createSearch( false, true );
0 ignored issues
show
Unused Code introduced by
The call to Aimeos\MShop\Common\Manager\Iface::createSearch() has too many arguments starting with true. ( Ignorable by Annotation )

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

148
		/** @scrutinizer ignore-call */ 
149
  $search = $manager->createSearch( false, true );

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress. Please note the @ignore annotation hint above.

Loading history...
149
150
		if( ( $key = $view->param( 'aggregate' ) ) !== null )
151
		{
152
			$search = $this->initCriteria( $search, $view->param() );
153
			$view->data = $manager->aggregate( $search, $key, $view->param( 'value' ), $view->param( 'type' ) );
154
			return $response;
155
		}
156
157
		$total = 1;
158
		$include = ( ( $include = $view->param( 'include' ) ) !== null ? explode( ',', $include ) : [] );
159
160
		if( ( $id = $view->param( 'id' ) ) == null ) {
161
			$search = $this->initCriteria( $search, $view->param() );
162
		} else {
163
			$search->setConditions( $search->compare( '==', 'order.base.id', $id ) );
164
		}
165
166
		$view->data = $manager->searchItems( $search, [], $total );
167
		$view->childItems = $this->getChildItems( $view->data, $include );
168
		$view->listItems = $this->getListItems( $view->data, $include );
169
		$view->refItems = $this->getRefItems( $view->listItems );
170
		$view->total = $total;
171
172
		return $response;
173
	}
174
175
176
	/**
177
	 * Returns the items with parent/child relationships
178
	 *
179
	 * @param \Aimeos\Map $items List of items implementing \Aimeos\MShop\Common\Item\Iface
180
	 * @param array $include List of resource types that should be fetched
181
	 * @return \Aimeos\Map List of items implementing \Aimeos\MShop\Common\Item\Iface
182
	 */
183
	protected function getChildItems( \Aimeos\Map $items, array $include ) : \Aimeos\Map
184
	{
185
		$list = map();
186
		$context = $this->getContext();
187
		$ids = $items->keys()->toArray();
188
189
		$domains = ['order/base/address', 'order/base/coupon', 'order/base/product', 'order/base/service'];
190
		$include = map( $domains )->intersect( $include );
191
192
		foreach( $include as $type )
193
		{
194
			$manager = \Aimeos\MShop::create( $context, $type );
195
196
			$search = $manager->createSearch( false, true );
0 ignored issues
show
Unused Code introduced by
The call to Aimeos\MShop\Common\Manager\Iface::createSearch() has too many arguments starting with true. ( Ignorable by Annotation )

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

196
			/** @scrutinizer ignore-call */ 
197
   $search = $manager->createSearch( false, true );

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress. Please note the @ignore annotation hint above.

Loading history...
197
			$search->setConditions( $search->combine( '&&', [
198
				$search->compare( '==', str_replace( '/', '.', $type ) . '.baseid', $ids ),
199
				$search->getConditions(),
200
			] ) );
201
202
			$list = $list->merge( $manager->searchItems( $search ) );
203
		}
204
205
		return $list;
206
	}
207
}
208