Issues (66)

src/Aimeos/Shop/Controller/CatalogController.php (12 issues)

1
<?php
2
3
/**
4
 * @license MIT, http://opensource.org/licenses/MIT
5
 * @copyright Aimeos (aimeos.org), 2015-2016
6
 * @package laravel
7
 * @subpackage Controller
8
 */
9
10
11
namespace Aimeos\Shop\Controller;
12
13
use Aimeos\Shop\Facades\Shop;
14
use Illuminate\Routing\Controller;
15
use Illuminate\Support\Facades\Response;
16
17
18
/**
19
 * Aimeos controller for catalog related functionality.
20
 *
21
 * @package laravel
22
 * @subpackage Controller
23
 */
24
class CatalogController extends Controller
25
{
26
	/**
27
	 * Returns the view for the XHR response with the counts for the facetted search.
28
	 *
29
	 * @return \Illuminate\Http\Response Response object with output and headers
30
	 */
31
	public function countAction()
32
	{
33
		foreach( app( 'config' )->get( 'shop.page.catalog-count' ) as $name )
34
		{
35
			$params['aiheader'][$name] = Shop::get( $name )->getHeader();
0 ignored issues
show
The call to Aimeos\Shop\Facades\Shop::get() has too many arguments starting with $name. ( Ignorable by Annotation )

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

35
			$params['aiheader'][$name] = Shop::/** @scrutinizer ignore-call */ get( $name )->getHeader();

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...
36
			$params['aibody'][$name] = Shop::get( $name )->getBody();
37
		}
38
39
		return Response::view( 'shop::catalog.count', $params )
0 ignored issues
show
Comprehensibility Best Practice introduced by Andreas
The variable $params seems to be defined by a foreach iteration on line 33. Are you sure the iterator is never empty, otherwise this variable is not defined?
Loading history...
40
			->header( 'Content-Type', 'application/javascript' )
41
			->header( 'Cache-Control', 'public, max-age=300' );
42
	}
43
44
45
	/**
46
	 * Returns the html for the catalog detail page.
47
	 *
48
	 * @return \Illuminate\Http\Response Response object with output and headers
49
	 */
50
	public function detailAction()
51
	{
52
		foreach( app( 'config' )->get( 'shop.page.catalog-detail' ) as $name )
53
		{
54
			$params['aiheader'][$name] = Shop::get( $name )->getHeader();
0 ignored issues
show
The call to Aimeos\Shop\Facades\Shop::get() has too many arguments starting with $name. ( Ignorable by Annotation )

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

54
			$params['aiheader'][$name] = Shop::/** @scrutinizer ignore-call */ get( $name )->getHeader();

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...
55
			$params['aibody'][$name] = Shop::get( $name )->getBody();
56
		}
57
58
		return Response::view( 'shop::catalog.detail', $params )
0 ignored issues
show
Comprehensibility Best Practice introduced by Andreas
The variable $params seems to be defined by a foreach iteration on line 52. Are you sure the iterator is never empty, otherwise this variable is not defined?
Loading history...
59
			->header( 'Cache-Control', 'private, max-age=10' );
60
	}
61
62
63
	/**
64
	 * Returns the html for the catalog list page.
65
	 *
66
	 * @return \Illuminate\Http\Response Response object with output and headers
67
	 */
68
	public function listAction()
69
	{
70
		foreach( app( 'config' )->get( 'shop.page.catalog-list' ) as $name )
71
		{
72
			$params['aiheader'][$name] = Shop::get( $name )->getHeader();
0 ignored issues
show
The call to Aimeos\Shop\Facades\Shop::get() has too many arguments starting with $name. ( Ignorable by Annotation )

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

72
			$params['aiheader'][$name] = Shop::/** @scrutinizer ignore-call */ get( $name )->getHeader();

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...
73
			$params['aibody'][$name] = Shop::get( $name )->getBody();
74
		}
75
76
		return Response::view( 'shop::catalog.list', $params )
0 ignored issues
show
Comprehensibility Best Practice introduced by Andreas
The variable $params seems to be defined by a foreach iteration on line 70. Are you sure the iterator is never empty, otherwise this variable is not defined?
Loading history...
77
			->header( 'Cache-Control', 'private, max-age=10' );
78
}
79
80
81
	/**
82
	 * Returns the html body part for the catalog stock page.
83
	 *
84
	 * @return \Illuminate\Http\Response Response object with output and headers
85
	 */
86
	public function stockAction()
87
	{
88
		foreach( app( 'config' )->get( 'shop.page.catalog-stock' ) as $name )
89
		{
90
			$params['aiheader'][$name] = Shop::get( $name )->getHeader();
0 ignored issues
show
The call to Aimeos\Shop\Facades\Shop::get() has too many arguments starting with $name. ( Ignorable by Annotation )

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

90
			$params['aiheader'][$name] = Shop::/** @scrutinizer ignore-call */ get( $name )->getHeader();

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...
91
			$params['aibody'][$name] = Shop::get( $name )->getBody();
92
		}
93
94
		return Response::view( 'shop::catalog.stock', $params )
0 ignored issues
show
Comprehensibility Best Practice introduced by Andreas
The variable $params seems to be defined by a foreach iteration on line 88. Are you sure the iterator is never empty, otherwise this variable is not defined?
Loading history...
95
			->header( 'Content-Type', 'application/javascript' )
96
			->header( 'Cache-Control', 'public, max-age=30' );
97
	}
98
99
100
	/**
101
	 * Returns the view for the XHR response with the product information for the search suggestion.
102
	 *
103
	 * @return \Illuminate\Http\Response Response object with output and headers
104
	 */
105
	public function suggestAction()
106
	{
107
		foreach( app( 'config' )->get( 'shop.page.catalog-suggest' ) as $name )
108
		{
109
			$params['aiheader'][$name] = Shop::get( $name )->getHeader();
0 ignored issues
show
The call to Aimeos\Shop\Facades\Shop::get() has too many arguments starting with $name. ( Ignorable by Annotation )

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

109
			$params['aiheader'][$name] = Shop::/** @scrutinizer ignore-call */ get( $name )->getHeader();

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...
110
			$params['aibody'][$name] = Shop::get( $name )->getBody();
111
		}
112
113
		return Response::view( 'shop::catalog.suggest', $params )
0 ignored issues
show
Comprehensibility Best Practice introduced by Andreas
The variable $params seems to be defined by a foreach iteration on line 107. Are you sure the iterator is never empty, otherwise this variable is not defined?
Loading history...
114
			->header( 'Cache-Control', 'private, max-age=300' )
115
			->header( 'Content-Type', 'application/json' );
116
	}
117
118
119
	/**
120
	 * Returns the html for the catalog tree page.
121
	 *
122
	 * @return \Illuminate\Http\Response Response object with output and headers
123
	 */
124
	public function treeAction()
125
	{
126
		foreach( app( 'config' )->get( 'shop.page.catalog-tree' ) as $name )
127
		{
128
			$params['aiheader'][$name] = Shop::get( $name )->getHeader();
0 ignored issues
show
The call to Aimeos\Shop\Facades\Shop::get() has too many arguments starting with $name. ( Ignorable by Annotation )

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

128
			$params['aiheader'][$name] = Shop::/** @scrutinizer ignore-call */ get( $name )->getHeader();

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...
129
			$params['aibody'][$name] = Shop::get( $name )->getBody();
130
		}
131
132
		return Response::view( 'shop::catalog.tree', $params )
0 ignored issues
show
Comprehensibility Best Practice introduced by Andreas
The variable $params seems to be defined by a foreach iteration on line 126. Are you sure the iterator is never empty, otherwise this variable is not defined?
Loading history...
133
			->header( 'Cache-Control', 'private, max-age=10' );
134
	}
135
}